JMX Monitor
You can use the JMX Monitor to poll available managed beans (MBeans) on Java application servers and JVMs with SAM.
This predefined component monitor is included in the following SAM application monitor templates:
Because MBeans can vary widely in different environments, you can also create custom JMX monitors to pull specific MBeans from target servers.
Note the following details about JMX Monitors"
- You may need JMX credentials or none at all, depending on how the Java application server is configured.
- The following SolarWinds Platform features do not support JMX monitoring:
- To set up target servers for monitoring, see Configure Java application servers and JVMs for SAM monitoring.
- The JMX Monitor supports SolarWinds Platform agents for Windows, Linux, and AIX. For Linux servers, see Configure Linux/Unix systems for monitoring by the SolarWinds Platform agent in SAM.
Agentless and SolarWinds Platform agent for Windows polling use the JMX Bridge Service but Linux-based JMX queries run locally through the SolarWinds Platform agent itself. For details, see this THWACK post.
- (Recommended) To monitor Apache Tomcat servers, use a template that includes a Tomcat Server monitor, such as the Tomcat Server template.
- Numeric values for the following data types are supported:
- java.lang.Byte
- java.lang.Short
- java.lang.Integer
- java.lang.Long
- java.lang.Double
- java.lang.Float
To monitor string data, consider creating a custom script monitor.
Recommended: Test JMX components individually to avoid heavy loads on agents.
Field descriptions
Description
A default description of the monitor. To override the default description, add to or replace existing text. Changes are automatically saved. The variable to access this field is ${UserDescription}
.
Customize descriptions to specify what will be monitored so related alerts and notifications are more meaningful later.
Component Type
The type of monitor being used.
Enable Component
Determines if a component is enabled. Disabling a component leaves it in the application as deactivated and does not influence application availability or status, as displayed in the SolarWinds Platform Web Console.
Credential for Monitoring
Provide JMX credentials to query MBeans. You may need JMX credentials to query MBeans or none at all, depending on how the Java application server is configured.
Select a credential from the list provided or use the <Inherit credential from node> option. If the credential you need is not in the credentials list, add it in the SAM Credentials Library.
Count statistic as difference
Select this option to change the statistic to be the difference in query values between polling cycles. This measure is the difference in polled values and trend that statistic. This is a constantly increasing value, as it tracks total collection time since the JVM started.
Port Number
Specify the port number used for JMX connections.
Protocol
Choose between using Remote Method Invocation (RMI) and Invocation over Internet Inter-Orb Protocol (IIOP).
URL Path
The last part of the JMX service URL, which follows hostname:portnumber
and begins with a slash. For example: service:jmx:rmi:///jndi/rmi://HostName:portnumber/jmxrmi
Custom URL Format
(Optional) Enter a custom format for the URL. Use the following available macros: ${IP}
, ${PORT}
, ${PROTOCOL}
, or ${PATH}
, or leave the field empty to use the default format.
Object Name
The unique string identifier of an MBean in the form of <domain -name>:<key property >
.
Attribute Name
The name of an MBean attribute.
Key
This can be used to monitor composite attributes, which consist of key:value
pairs.
Convert Value
Select the "Yes, convert returned value" option to display fields where you can select a common function or enter a custom formula. The Custom Conversion option provides basic arithmetic operators (+, -, *, /), plus built-in mathematical functions for more advanced conversions. See Convert values in data transformations for SAM component monitors.
Statistic Threshold
Specify a threshold that indicates a warning or critical level was breached. Logical operators are in the drop-down list, followed by a blank field where you can enter the value of this threshold. For example: Less than 15
for warning, Less than 5
for critical. See Application Monitor Thresholds.
User Notes
Add notes for easy reference, accessible by using the variable, ${UserNotes}
.