MySQL 5.5.62 • MariaDB 10.0.37 • PostgreSQL 9.2.24 • Oracle 11.2 TimescaleDB native compression support TimescaleDB native compression is now supported in Zabbix server installations with PostgreSQL version templates are available for monitoring: Elasticsearch • Template App Elasticsearch Cluster by HTTP - native template to monitor Elasticsearch. ClickHouse • Template DB ClickHouse - collects node metrics version. Then, while in Configuration → Templates you can import them manually into Zabbix. Items Native support of the system.swap.size[,] metric has been added to Zabbix agent 2. See also:

Optimized SNMP discovery and collection SNMP discovery and data collection has been updated to use native SNMP bulk requests (GetBulkRequest-PDUs), available in SNMP versions 2/3. A GetBulk request in option in Zabbix has been retained (under a new name ”use combined requests”). This is not related to native SNMP bulk requests in any way; it is Zabbix own way of combining multiple SNMP requests. See also: should the current service fail. Zabbix offers a native high-availability solution that is easy to set up and does not require any previous HA expertise. Native Zabbix HA may be useful for an extra layer of

should the current service fail. Zabbix offers a native high-availability solution that is easy to set up and does not require any previous HA expertise. Native Zabbix HA may be useful for an extra layer of The native HA solution is designed to be simple in use, it will work across sites and does not have specific requirements for the databases that Zabbix recognizes. Users are free to use the native Zabbix particular machine that reported the failure. Zabbix agents are extremely efficient because of use of native system calls for gathering statistical information. Passive and active checks Zabbix agents can

changes for this version. High availability cluster for Zabbix server The new version comes with a native high availability solution for Zabbix server. The solution consists of multiple zabbix_server instances differently - see Known issues for details. 6 What’s new in Zabbix 6.0.1 Zabbix agent 2 items • Native support for the items net.dns and net.dns.record has been added. These items, used with Zabbix agent should the current service fail. Zabbix offers a native high-availability solution that is easy to set up and does not require any previous HA expertise. Native Zabbix HA may be useful for an extra layer of

monitoring of Cloudflare web traffic and DNS metrics via HTTP; • Website certificate by Zabbix agent 2 - native monitoring of TLS/SSL website certificates by Zabbix agent 2. You can get these templates: • In Then, while in Configuration → Templates you can import them manually into Zabbix. Item changes Native support for the items system.hw.chassis, system.hw.devices, vfs.dir.count, and vfs.dir.size has been M.A.R.T. plugin, have been updated and now return {#DISKTYPE} macro value in the lower case. • Native support for the items net.dns and net.dns.record has been added to Zabbix agent 2. These items, used

See also: Windows Zabbix agent items Low-level discovery of OS processes Zabbix now provides a native solution to discover running OS processes. A new item proc.get[] can be used in discovery rules to should the current service fail. Zabbix offers a native high-availability solution that is easy to set up and does not require any previous HA expertise. Native Zabbix HA may be useful for an extra layer of The native HA solution is designed to be simple in use, it will work across sites and does not have specific requirements for the databases that Zabbix recognizes. Users are free to use the native Zabbix

particular machine that reported the failure. Zabbix agents are extremely efficient because of use of native system calls for gathering statistical information. Passive and active checks Zabbix agents can however, there are some systems where that may need to be set specifically. 5 Java gateway Overview Native support for monitoring JMX applications exists in the form of a Zabbix daemon called ”Zabbix Java Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, e.g. E:\openssl-1.1

automatically extract a macro and value if an array field uses the {#MACRO} syntax as a key. Any new native discovery checks will use the new syntax without the ”data” elements. When processing a low-level the root is located (array at $. or $.data). While the ”data” element has been removed from all native items related to discovery, for backward compatibility Zabbix will still accept the JSON notation particular machine that reported the failure. Zabbix agents are extremely efficient because of use of native system calls for gathering statistical information. Passive and active checks Zabbix agents can

particular machine that reported the failure. Zabbix agents are extremely efficient because of use of native system calls for gathering statistical information. Passive and active checks Zabbix agents can however, there are some systems where that may need to be set specifically. 5 Java gateway Overview Native support for monitoring JMX applications exists in the form of a Zabbix daemon called ”Zabbix Java Unpack OpenSSL sources, for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, e.g. E:\openssl-1.1

mysql> CREATE USER 'zbx_srv'@'%' IDENTIFIED WITH mysql_native_password BY '', 'zbx_web'@'%' IDENTIFIED WITH mysql_native_password BY '' REQUIRE SSL PASSWORD HISTORY user: mysql> CREATE USER 'zbx_srv'@'%' IDENTIFIED WITH mysql_native_password BY '', 'zbx_web'@'%' IDENTIFIED WITH mysql_native_password BY '' REQUIRE X509 PASSWORD HISTORY optimize PostgreSQL configuration parameters in your postgresql.conf. TimescaleDB compression Native TimescaleDB compression is supported starting from Zabbix 5.0 for PostgreSQL version 10.2 or higher