JMX Sensor


Migrated from NovaTec Jira. Originalticket: INSPECTIT-33

inspectIT should allow to query JMX metrics. The goal is to allow the inspectIT agent to read JMX metrics from the instrumented server (e.g. the application server). The approach must adhere to the current push approach of inspectIT. A configuration should allow the definition of the JMX server and the data to be queried




Ivan Senic
January 6, 2016, 11:58 AM

Everything works, just some small clarifications..

Ivan Senic
December 23, 2015, 11:07 AM

Rebase conflicts, other than that perfect

Ivan Senic
December 10, 2015, 9:22 AM

Some small comments, should be easy

Marius Oehler
December 8, 2015, 1:58 PM

I've implemented the comments from reviewable though more code had to be adapted than I thought.

I measured the runtime of the "registerMBeans(..)" method in the environment of a simple calculator application and in a tomcat whereat I found and fixed some big bugs in the registration process of the Jmx sensor and it's sensor types.

The measurement results are shown in the attached image:

The runtime was measured by wrapping the method call with Java's System.nanoTime() and calculating the time difference between the before and after "timestamp".

The runtime of the registerMBeans method was between 140us and 400us when the calculator app was used which exposed 19 mBeans (default JVM beans). The runtime grew up to 2.7ms while 6 attributes were registered (comprised registration time of the CMR, network...).

The runtime of the registerMBeans method was between 150us and 390us when tomcat was used. Here, up to 145 mBeans were exposed by tomcat.
Overall, the duration without registration a mBean is in a similar magnitude regardless the number of exposed mBeans.

Ivan Senic
December 3, 2015, 10:40 AM

Moving to failed integration until latest additions from are pushed..



Marius Oehler


Stefan Siegl


Ivan Senic