Running at scale successfully in large production environments we The Jar has been included in our agent since 2015 and has been To make it even simpler to include in our Python plugins I have also created a new Python module to access the Jar, also called jmxquery, which installs with the Jar bundled inside the module.
The result is JMXQuery which I am open sourcing after 3.5 years today!, It’s a very small, lightweight Jar (17kb) that provides a command line interface to a JMX port on any JVM greater than version 1.5. So in the end I decided to write an integration The command line dynamically didn’t fit into the plugin editorĮxperience I wanted. I also looked at JMXTransīut the fact it required configuration files and couldn’t be run from
Macjournal import .jmx install#
With our agent install to ensure it worked anywhere, which would haveĮxploded the package size.
Python plugins to Java via JMX, such as JPype,īut they weren’t very portable and would have required embedding a JVM I looked around for ways to interface our I wanted something that would work out of the box, and allows user toĮasily create plugins with our built in plugin editor just as easily asĪny other non-Java service. It was frustrating that our users could monitor non-Java services in a few clicks but the moment they wanted to monitor Java we had to get them to install 3rd party agents, and there were so many ways of doing it there was no consistent way we could rely on to make it a one click setup like our non-Java integrations.
At that time we were recommending new users monitor Java services using solutions like Jolokia, listed in this blog we wrote back then. Introducing JMXQuery to Monitor Java via Python March 14, 2018īack in December 2014, we had a team Christmas hackathon and I decided I wanted to make Java Monitoring really simple via our agent and integration plugins.
0 kommentar(er)
