Go to All Forums

JMX Monitor as an extra Monitor instead of fully APM agent

Hello,

we would like to have the possibility to have an extra JMX monitor (as basic monitor) instead of using a full APM agent.

We often interested only in few basic information like JVM runtime metrics and not in tracing transactions or general deep insight into the application.

The JMX Monitor should have the same functionality as the JVM section under APM for java and App parameters (blocked threads, thread count usage for connectors ...).

And it should have the possibility to add some own mbean metrics under app parameters.

This JMX Monitor could be a central agent which connects remotely to the JVMs.

Thanks and regards,

Torsten

 

 

Like (2) Reply
Replies (2)

Re: JMX Monitor as an extra Monitor instead of fully APM agent

Hi Torsten,

We have developed JVM and JVM Memory plugins which would monitor the metrics using JMX shown under the JVM tab in the APM monitors. Please follow the ReadME of the plugins for detailed installation and configuration.

These plugins use Java to access the JMX MBeans and get the data. A server agent is required to execute the plugins and upload the data to Site24x7 servers. 

To monitor more JMX metrics, you can download JMX plugin from GitHub and configure the MBean to be monitored in metrics.txt

You can also configure the remote JVM application in the host and port in the sh files. Each plugin would be considered a basic monitor and can monitor upto 25 metrics per plugin.

Hope this helps!

 

Regards,

Anita

Like (1) Reply

Re: Re: JMX Monitor as an extra Monitor instead of fully APM agent

Hi Anita,

 

I tested it and it works for my use cases!

Had to change some things:

- wget doesn't work, wrong url

- added correct metric types (bytes, percentage..)

- put everything together in one script.

 

Very cool!

Thank you very much!

-Torsten

Like (0) Reply

Was this post helpful?