Applications Systems

Configuring JMX for JVM monitoring in SAM

This article describes how to configure JMX for JVM monitoring in SAM, which involves gathering server configuration details and using the JMX component monitor wizard to add the monitor to your environment.

First published date

10/24/2018 2:51 PM

Last published date

11/30/2021 9:00 AM

Overview

Before proceeding with this article, please note that SAM 2020.2 includes the following JMX monitoring updates:

The Orion Platform now includes OpenJDK 14.0.
To configure target servers for JMX monitoring, you can use OpenJDK or a commercial version of Java SE.
The JMX probe for Linux now supports OpenJDK 14.0.
The Oracle WebLogic (JMX) template was updated to support WebLogic 12.2.1.3.0.

For the latest details, see Configure Java application servers and JVMs for SAM monitoring.

Product section

Server Application Monitor

Resolution

Java Management Extensions (JMXs) allow remote clients to manage and monitor applications in Java Virtual Machine (JVM) environments via Managed Beans (MBeans). MBeans are the controllable end-points of an application that enable remote clients to monitor activity, as well as collect statistics such as performance, resource usage, and troubleshooting data. Similar to JavaBeans, MBeans are managed Java objects that follows design patterns set in the JMX specification.

To access JMX data in SAM:

Gather server configuration details, including server IP address, port number, protocol type, URL path, and credentials.
Prepare target servers. See Configure Java application servers and JVMs for SAM monitoring.
Use the JMX component monitor wizard to add the monitor to your environment. Here is an example of the wizard's MBeans page:

Insert this argument in the Java command that publishes the platform MBean server to your local environment: Dcom.sun.management.jmxremote

After the JMX Component Monitor is implemented, the following sample figure shows how MBean data appears in SAM:

Note: JConsole is a free GUI-based JVM environment monitoring tool that is not required by the JMX Component Monitor in SAM but it is useful for Java monitoring. You can download it here here

Additional resources include:

Java arguments for remote JMX monitoring
Monitoring Those Hard to Reach Places: Linux, MySQL, Oracle, Java and More (video)
Understanding Java Remote JMX - Initial setup/configuration overview (THWACK)
Understanding Java Remote JMX - SAM Template Config (THWACK)
Update the JDK and JRE for Orion Platform products (SolarWinds Success Center)

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.