Improve the Java VM monitoring via better Jolokia plug-in

70 votes

The current jolokia plug-in needs an update to monitor, what is needed on the Java side

Under consideration Checks&Agents Suggested by: Thomas Lippert (08 May, '22) • Upvoted: 03 May • Comments: 4

Comments: 4

10 May, '22
Mike1098
Allow to assign a metric name to custom beans.
Currently its only possible to assign one metric definition to custom beans.
If custom beans defined with numeric output and different units like MByte, % etc. it should be possible to assign a metric definition for each unit.
12 May, '22
Lars Sörensen
It would also be helpful if there were more predefined sets of metrics (keyword MBEAN_SECTIONS_SPECIFIC) for widely used applications such as Jira, Confluence, Tomcat, Jboss, Jboss EAP, Websphere, Jetty, Activemq, Kafka etc..

These could be stored in separate files, making it easier for the community to exchange, customize, extend, and maintain.

In the CGF file you could then specify for each instance which sets should be used in the event that the autodetection does not work or is unknown. This would also allow you to specify custom MBeans for only one instance instead for all instances as is the case today.
24 Nov, '23
Mike1098
My vote is the third time removed from here :-(
01 Dec, '23
Niklas Pulina Admin
Hello Mike1098, our Ideas Portal is built on a third-party platform that has a built-in throttling mechanism for votes.

For details, please see https://help.featureupvote.com/article/71-throttling

While we can change a few (very basic) settings here, we have no influence on the underlying mechanism. If you have the feeling that your vote was removed by this throttling mechanism, please feel invited to vote again. Sorry for the inconvenience.

Warm regards,
Your Checkmk team