gathering • availability and performance checks • support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy library has been discontinued. JMX monitoring attributes with tabular data Support of tabular data objects in JMX Mbean attributes has been added. It is supported for the JMX agent data collection and low-level monitoring: Apache projects • Apache Cassandra by JMX - see setup instructions for JMX templates; • Apache Kafka by JMX - - see setup instructions for JMX templates; • Hadoop by HTTP - see setup instructions

gathering • availability and performance checks • support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy specified interface (or several interfaces). All four interface types are supported: Zabbix agent, IPMI, JMX, SNMP. If Custom is set, but no interfaces have been specified - the hosts will be created without out-of-the-box monitoring: • Apache Cassandra by JMX - see setup instructions for JMX templates. • Apache Kafka by JMX - see setup instructions for JMX templates. You can get these templates: • In Configuration

gathering • availability and performance checks • support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy internal items now support a pused mode, returning the use percentage of the respective buffer. JMX monitoring 19 Zabbix Java gateway now supports working with custom MBeans returning non-primitive where that may need to be set specifically. 4 Java gateway Overview Native support for monitoring JMX applications exists in the form of a Zabbix daemon called ”Zabbix Java gateway”, available since Zabbix

gathering • availability and performance checks • support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy value preprocessing options and more details, see Item configuration. 8 Configurable JMX endpoints Previously, a JMX endpoint was hardcoded in Zabbix, which was limiting given that there are applications endpoints. To lift this limitation, support for configurable JMX endpoints has been added as a separate field in JMX item configuration. When you open a JMX item, initially the field is filled with the default

gathering • availability and performance checks • support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy Discovery of systemd services • Zabbix agent items (new item keys) JMX MBean discovery with non-ASCII characters There is now a new item for JMX MBean discovery that does not generate low-level discovery macros square brackets and non-ASCII characters): jmx.get[,] The jmx.discovery[] item from previous versions, if it encountered JMX MBean properties that could not be converted

gathering • availability and performance checks • support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy where that may need to be set specifically. 4 Java gateway Overview Native support for monitoring JMX applications exists in the form of a Zabbix daemon called ”Zabbix Java gateway”, available since Zabbix 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 JMX management API to query the application of interest remotely

IP address for: - outgoing connections to Zabbix server; - agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks); - HTTP agent connections; - script item JavaScript HTTP requests; empty string jmx_available number JMX agent availability 0, HOST_AVAILABLE_UNKNOWN - unknown 1, HOST_AVAILABLE_TRUE - available 2, HOST_AVAILABLE_FALSE - unavailable jmx_error string JMX agent error "ipmi_error":"", "jmx_available":0, "jmx_error":"" }, { "hostid":10107, "available":1, "error":"", "snmp_available":0, "snmp_error":"", "ipmi_available":0, "ipmi_error":"", "jmx_available":0, "jmx_error":""

gathering • availability and performance checks • support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy Availability icons in the frontend are now only displayed for those interfaces (Zabbix agent, SNMP, IPMI, JMX) that have been configured on the host • If you position the mouse over the availability icon, a from pollers Direct connections to database have been removed from pollers, unreachable pollers and JMX pollers on Zabbix server/proxy. Previously these connections were required for: • Calculated items

IP address for: - outgoing connections to Zabbix server; - agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks); - HTTP agent connections SSHKeyLocation no Location of public empty string jmx_available number JMX agent availability 0, HOST_AVAILABLE_UNKNOWN - unknown 1, HOST_AVAILABLE_TRUE - available 2, HOST_AVAILABLE_FALSE - unavailable jmx_error string JMX agent error "ipmi_error":"", "jmx_available":0, 149 "jmx_error":"" }, { "hostid":10107, "available":1, "error":"", "snmp_available":0, "snmp_error":"", "ipmi_available":0, "ipmi_error":"", "jmx_available":0, "jmx_error":""

gathering • availability and performance checks • support for SNMP (both trapping and polling), IPMI, JMX monitoring • custom checks • gathering desired data at custom intervals • performed by server/proxy and item mass update form interfaces are grouped by their type. 5.1.5 Direct JMX monitoring support Ability to monitor JMX without deploying additional software has been introduced in the form of a Java added. It allows to properly monitor host availability by each of states - Zabbix agent, SNMP, IPMI, JMX - and returns values for available, unavailable and unknown. The database upgrade process doesn’t