Zabbix Documentation 3.2

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:config:items:itemtypes:jmx_monitoring

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:config:items:itemtypes:jmx_monitoring [2015/10/20 11:04]
martins-v removing descriptions regarding 1.8 version from jmx monitoring section; adopting a more concise style
manual:config:items:itemtypes:jmx_monitoring [2017/10/23 15:24] (current)
martins-v communication between Java gateway and the monitored JMX application should not be firewalled
Line 1: Line 1:
-==== - #14 JMX monitoring ====+==== 14 JMX monitoring ====
  
 === - Overview === === - Overview ===
Line 9: Line 9:
 To retrieve the value of a particular JMX counter on a host, Zabbix server queries the Zabbix **Java gateway**, which in turn uses the [[http://​java.sun.com/​javase/​technologies/​core/​mntr-mgmt/​javamanagement/​|JMX management API]] to query the application of interest remotely. To retrieve the value of a particular JMX counter on a host, Zabbix server queries the Zabbix **Java gateway**, which in turn uses the [[http://​java.sun.com/​javase/​technologies/​core/​mntr-mgmt/​javamanagement/​|JMX management API]] to query the application of interest remotely.
  
-<​note>​See the respective manual section for setup and more details ​on Zabbix ​[[/​manual/​concepts/​java|Java gateway]].</​note>​+For more details ​and setup see the [[/​manual/​concepts/​java|Zabbix ​Java gateway]] ​section. 
 + 
 +<note warning>​Communication between Java gateway and the monitored JMX application should not be firewalled.</​note>​
  
 === - Enabling remote JMX monitoring for Java application === === - Enabling remote JMX monitoring for Java application ===
Line 24: Line 26:
   -jar /​usr/​share/​doc/​openjdk-6-jre-headless/​demo/​jfc/​Notepad/​Notepad.jar   -jar /​usr/​share/​doc/​openjdk-6-jre-headless/​demo/​jfc/​Notepad/​Notepad.jar
  
-This makes Java listen for incoming JMX connections on port 12345 and tells it not to require authentication or SSL.+This makes Java listen for incoming JMX connections on port 12345, from local host only, and tells it not to require authentication or SSL.  
 + 
 +If you want to allow connections on another interface, set the -Djava.rmi.server.hostname parameter to the IP of that interface.
  
 If you wish to be more stringent about security, there are many other Java options available to you. For instance, the next example starts the application with a more versatile set of options and opens it to a wider network, not just local host. If you wish to be more stringent about security, there are many other Java options available to you. For instance, the next example starts the application with a more versatile set of options and opens it to a wider network, not just local host.
Line 63: Line 67:
 For each JMX counter you are interested in you add an item of type **JMX agent** attached to that interface. If you have configured authentication on your Java application,​ then you also specify username and password. ​ For each JMX counter you are interested in you add an item of type **JMX agent** attached to that interface. If you have configured authentication on your Java application,​ then you also specify username and password. ​
  
-The key in the screenshot below says ''​%%jmx["​java.lang:​type=Memory","​HeapMemoryUsage.used"​]%%''​. The JMX item key syntax is similar to Zapcat items, except that a comma is used for separating arguments instead of "​]["​. The key consists of 2 parameters:+The key in the screenshot below says ''​%%jmx["​java.lang:​type=Memory","​HeapMemoryUsage.used"​]%%''​. The key consists of 2 parameters:
  
   * object name - which represents the object name of an MBean   * object name - which represents the object name of an MBean