Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
JMX Active Discovery can discover:
JMX Active Discovery can also discover multiple Java instances on a device listening on multiple ports, and then discover all the objects on each port, creating an array of objects.
Device properties jmx.user and jmx.pass are used for authentication information.
The parameters for JMX Discovery are:
For example, the configuration in the image below would list all the threadpools on a Tomcat server:
If the attribute specified in the JMX Path parameter is:
Where a list of ports (or a token such as jmx.ports that is replaced with a list of ports) is given in the Portsfield, ##WILDVALUE## is substituted for the port at collection time, while ##WILDVALUE2## is substituted for the discovered JMX object (or attribute.)
If an attribute value or values are to be discovered (instead of an MBean object name), the attribute should be separated from the object by a colon. For example, to discover an instance with the value of the serverInfo attribute of the Server Mbean in the Catalina domain, specify a JMX Path of “Catalina:type=Server:serverInfo”
This would return an instance with the value of the attribute serverInfo as returned by the Tomcat server, such as “Apache Tomcat/5.5.25”. This value could then be used in filtering, if desired.
JMX filtering can be applied to either the port, the discovered MBean paths, or to the discovered attribute values.
If the attribute specified in the filter is a path, or path component, it will be treated as a string. You can include the variable discovered part of the path by use of the ##WILDVALUE## token, or the ##WILDVALUE2## if using port discovery also.
e.g. If you were discovering path=”Catalina:type=Manager,host=localhost,path=*”
and the returned results were:
You could include only your specific applications by adding a filter:
An alternative way of filtering is based on attribute values. You could, for example, create a filter that dynamically included all paths that have ever had any valid sessions:
For examples of JMX Active Discovery in action, see the datasources JVM Memory Pools- or Tomcat Sessions-.
In This Article