With Ruxit JMX monitoring extensions you can monitor anything in your JVM.
For a while now it’s been possible to track JMX (Java Managed Extensions) monitoring metrics for Tomcat, Jetty, and others. We’re now making this functionality available to you in Ruxit!
How to create a JMX extension
- Create a JSON file that describes your JMX metrics and how you want to display them. You’ll find a description and examples on the Ruxit GitHub page.
- To add your extension to Ruxit, go to Settings > Monitoring extensions and click Upload custom extension.
- Select the
plugin.jsonfile of your JMX extension.
Once successfully uploaded, your extension is listed on the Monitoring extensions page.
Note: If in the future you make changes to your plugin, remember to upload the updated file version to Ruxit.
You don’t need to restart your JVM to enable JMX extensions or make changes effective. Once your plugin is uploaded, Ruxit automatically begins querying the defined metrics for all Java processes. These metrics are displayed on each relevant process page. If you’ve defined key metrics, you’ll see those metrics included in the infographic. If you defined key charts you’ll see those metrics displayed in an aggregate form beneath the infographic (see the HornetQ example below).
Click the Further details tab to see all defined metrics. As described on the Ruxit GitHub page, Ruxit allows you to select any MBeans key property for viewing. The queue name property was selected for the example below.
Not seeing a certain metric for your JVM? JMX monitoring is highly dynamic. If a particular metric doesn’t exist in your JVM, it’s not an error—the metric simply isn’t available.