Zabbix Documentation 3.2

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:concepts:java

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:concepts:java [2015/03/13 09:58]
asaveljevs [Overview] mention 2.0.15 and 2.2.10 versions
manual:concepts:java [2017/08/24 19:31] (current)
martins-v removing auto numbering
Line 1: Line 1:
-==== - #5 Java gateway ====+==== 5 Java gateway ====
  
 === Overview === === Overview ===
  
-Zabbix 2.0 adds native ​support for monitoring JMX applications ​by introducing ​new Zabbix daemon called "​Zabbix Java gateway"​. Zabbix Java gateway is a daemon written in Java. When Zabbix server wants to know the value of a particular JMX counter on a host, it asks Zabbix Java gateway, which uses the [[http://​java.sun.com/​javase/​technologies/​core/​mntr-mgmt/​javamanagement/​|JMX management API]] to query the application of interest remotely. The application does not need any additional software installed, it just has to be started with ''​-Dcom.sun.management.jmxremote''​ option on the command line.+Native ​support for monitoring JMX applications ​exists in the form of a Zabbix daemon called "​Zabbix Java gateway"​, available since Zabbix 2.0. Zabbix Java gateway is a daemon written in Java. To find out the value of a particular JMX counter on a host, Zabbix server queries ​Zabbix Java gateway, which uses the [[http://​java.sun.com/​javase/​technologies/​core/​mntr-mgmt/​javamanagement/​|JMX management API]] to query the application of interest remotely. The application does not need any additional software installed, it just has to be started with ''​-Dcom.sun.management.jmxremote''​ option on the command line.
  
 Java gateway accepts incoming connection from Zabbix server or proxy and can only be used as a "​passive proxy"​. As opposed to Zabbix proxy, it may also be used from Zabbix proxy (Zabbix proxies cannot be chained). Access to each Java gateway is configured directly in Zabbix server or proxy configuration file, thus only one Java gateway may be configured per Zabbix server or Zabbix proxy. If a host will have items of type **JMX agent** and items of other type, only the **JMX agent** items will be passed to Java gateway for retrieval. Java gateway accepts incoming connection from Zabbix server or proxy and can only be used as a "​passive proxy"​. As opposed to Zabbix proxy, it may also be used from Zabbix proxy (Zabbix proxies cannot be chained). Access to each Java gateway is configured directly in Zabbix server or proxy configuration file, thus only one Java gateway may be configured per Zabbix server or Zabbix proxy. If a host will have items of type **JMX agent** and items of other type, only the **JMX agent** items will be passed to Java gateway for retrieval.