4 ms·
Agent is also a long established term: https://www.eginnovations.com/blog/agentless-vs-agent-based-monitoring/ https://www.eginnovations.com/blog/agentless-vs-
by cstrahan 18d ago
Agent is also a long established term:
https://www.eginnovations.com/blog/agentless-vs-agent-based-monitoring/ https://www.eginnovations.com/blog/agentless-vs-agent-based-...
https://www.reddit.com/r/sysadmin/comments/js8h65/looking_for_a_workstation_performance_monitoring/ https://www.reddit.com/r/sysadmin/comments/js8h65/looking_fo...
https://www.ibm.com/docs/en/aix/7.2.0?topic=tools-performance-monitoring-agent https://www.ibm.com/docs/en/aix/7.2.0?topic=tools-performanc...
https://jolokia.org/agent/jvm.html https://jolokia.org/agent/jvm.html
https://www.oracle.com/technical-resources/articles/javase/jvm-tool-interface.html https://www.oracle.com/technical-resources/articles/javase/j...
- jaggederest 18d agoAppreciate the references, I was the New Relic Ruby agent maintainer in 2010, as an additional reference. And we called it an agent, because it was hosted on the customer's infrastructure, but they didn't maintain or control it, we did. Regrettably no license to kill, and not much in the way of secrecy or gadgetry.
- 27183 18d ago> no license to kill, and not much in the way of secrecy or gadgetry Insofar as you know.. there could be plenty of killer secrecy and gadgetry that was surreptitiously injected by your build/deployment/distribution systems ;)
- jaggederest 18d agoit was ruby, so I did in fact know ;) Edit: the customers, in some cases, did indeed run interpreters that were bad, but that's not my lookout! Buy me a fancy beverage and I'll tell you a story sometime