Build Your Own Monitoring

JMX is a technology used to monitor Java applications. JMX uses objects called MBeans to expose data and resources from Exalead CloudView.

You need to use a JMX client to retrieve probes from Exalead CloudView. In the example below, we use the JConsole included within your JDK.

JMX is no longer activated by default on the gateway since Exalead CloudView 2020x.R1.

To allow JMX, you need to add these extra args to the DeploymentInternal.xml gateway process in the <deploy:args> section:

<bee:StringValue value="-Dcom.sun.management.jmxremote" />
<bee:StringValue value="-Dcom.sun.management.jmxremote.port=JMXPORT_OUTSIDE_OF_CV_PORT_RANGE" />
<bee:StringValue value="-Dcom.sun.management.jmxremote.authenticate=false" />
<bee:StringValue value="-Dcom.sun.management.jmxremote.ssl=false" />

The JMX port of the gateway retrieves probes in MBeans/jrds/Management/Operations/getLastValues(hostname, probename), where:

• hostname is the hostname specified in Deployment.xml.

• probename is the name of the probe (that is, the file name without the .RRD extension). You can find names of available probes in <DATADIR>/perfmonitoring/probe/<HOSTNAME>/.

The procedure below only applies to JConsole on a specific probe. You may use other JMX clients and probe names to build your own monitoring.

1. Run the JConsole application.
2. Select the gateway process and click Connect.
   
   
3. Once connected, select the MBeans tab.
4. Select jrds > Management > Operations > getLastValues. The following screen displays.
   
   

5. Enter:

   • The hostname in the p1 field.

   • The name of the probe in the p2 field. For this example, enter du to display disk usage.

6. Click getLastValues. A pop-up window displays the values of the probe: