 |
-
Modify the Webserver start script.

From the steps above, uncommenting the said variables will allow the Webserver to run with the JMX flags. Once a Java application is run with JMX flags, JMX managers/clients such as JConsole and our JMX-Server plugin will now be able to monitor the MBean attributes (such as Memory) of the Java application
- Save the start script.
- Start the Webserver.
-
Configure the JMX-Server Sampler:
<sampler name="centos_jmx_server_webserver"> <sampleInterval> <data>1</data> </sampleInterval> <plugin> <jmx-server> <connectionSettings> <generic> <connectionSetting> <name>serviceURL</name> <value> <var ref="WebServerJMX"></var> </value> </connectionSetting> </generic> </connectionSettings> <aliases> <alias> <name>$1</name> <value> <data>java.lang:type=Memory,*</data> </value> <showCommands> <headlines>false</headlines> <tableColumns>false</tableColumns> </showCommands> </alias> </aliases> <columns> <column> <label>attribute</label> <rowTemplate> <data>HeapMemoryUsage</data> </rowTemplate> </column> <column> <label>committed</label> <rowTemplate> <data>$1.HeapMemoryUsage.committed</data> </rowTemplate> </column> <column> <label>init</label> <rowTemplate> <data>$1.HeapMemoryUsage.init</data> </rowTemplate> </column> <column> <label>max</label> <rowTemplate> <data>$1.HeapMemoryUsage.max</data> </rowTemplate> </column> <column> <label>used</label> <rowTemplate> <data>$1.HeapMemoryUsage.used</data> </rowTemplate> </column> </columns> <jproperties> <jproperty> <data>-Xint</data> </jproperty> </jproperties> <idAttributes></idAttributes> </jmx-server> </plugin> </sampler>
- Save the Gateway setup.
The resulting dataview will look something like this:

 |
This guide assumes that the Netprobe has been set up to run the JMX-Server plugin. For JMX plugin documentation, please refer to here: JMX documentation
|
|
Comments
0 comments
Please sign in to leave a comment.