SharePont Microsoft SharePoint by HTTP - see setup instructions for HTTP templates. MongoDB • MongoDB cluster by Zabbix agent 2 • MongoDB node by Zabbix agent 2 See setup instructions for Zabbix agent 2 templates monitoring of TiDB server of TiDB cluster via HTTP; • TiDB PD by HTTP - monitoring of PD server of TiDB cluster via HTTP; • TiDB TiKV by HTTP - monitor TiKV server of TiDB cluster via HTTP. See setup instructions SNMP agent; • Microsoft SharePoint by HTTP - see setup instructions for HTTP templates; • MongoDB cluster by Zabbix agent 2 - see setup instructions for Zabbix agent 2 templates; • MongoDB node by Zabbix

custom attribute values. The items vmware.hv.discovery[], used for hypervisor discovery, and vmware.cluster.discovery[], used for clusters discovery, now return information about resource pools. Active checks monitoring New items are now available for: • Monitoring VMware alarms: vmware.alarms.get[], vmware.cluster.alarms.get[], vmware.datastore.alarms.get[], vmware.dc.alarms.get[], vmware.hv.alarms.get[], vmware VMware components: vmware.cluster.tags.get[], vmware.datastore.tags.get[], vmware.dc.tags.get[], vmware.hv.tags.get[], vmware.vm.tags.get[]. • Returning property values: vmware.cluster.property[], vmware.datastore

New official templates are available for monitoring: Elasticsearch • Template App Elasticsearch Cluster by HTTP - native template to monitor Elasticsearch. ClickHouse • Template DB ClickHouse - collects Zabbix agent 2 active See setup instructions for Zabbix agent 2 templates. MongoDB • MongoDB cluster by Zabbix agent 2 • MongoDB node by Zabbix agent 2 See setup instructions for Zabbix agent 2 templates using Red Hat Marketplace requires the OpenShift cluster to be registered in the Market- place Portal, including the roll out of the PullSecret in your cluster. Failure to do so will result in an image pull

setup. 5 What’s new in Zabbix 6.0.0 See breaking changes for this version. High availability cluster for Zabbix server The new version comes with a native high availability solution for Zabbix server standby, ready to take over in case the current node is stopped or fails. See also: High availability cluster. Updated service monitoring Several updates have been made to the monitoring of services. Service official templates are available for monitoring. Kubernetes • Kubernetes nodes by HTTP • Kubernetes cluster state by HTTP • Kubernetes API server by HTTP • Kubernetes Controller manager by HTTP • Kubernetes

What’s new in Zabbix 6.4.5 Templates New templates are available: • AWS ECS Cluster by HTTP (along with its Serverless Cluster version) • Cisco SD-WAN by HTTP • OpenStack by HTTP, which includes OpenStack manually into Zabbix. 22 Updated templates Integration with OpenShift has been added to Kubernetes cluster state by HTTP template. 15 What’s new in Zabbix 6.4.10 TimescaleDB 2.13 support Support for TimescaleDB features such as Failover Cluster Instances (FCI) and Availability Groups (AG). It is now possible to use the template for monitoring a host in cluster, standalone host and host by cluster name. A macro for

connector - statistics for connectors with the largest queue ha_status Log high availability (HA) cluster status. ha_remove_node=target Remove the high availability (HA) node specified by its name or ID Zabbix high availability mode multiple Zabbix servers are run as nodes in a cluster. While one Zabbix server in the cluster is active, others are on standby, ready to take over if necessary. 24 Switching Enabling high availability Starting Zabbix server as cluster node Two parameters are required in the server configuration to start a Zabbix server as cluster node: • HANodeName parameter must be specified

setupfor more information. Items VMware cluster performance counters A new vmware.cl.perfcounter[,,,] item allows to retrieve VMware cluster performance counter metrics. JMX items allows to define and execute transformation rules for the received item values. Preprocessing is managed by a preprocessing manager process, which was added in Zabbix 3.4, along with preprocessing workers Key Description Return value Parameters Comments ceph.df.details [connString, , ] Cluster’s data usage and distribution among pools. JSON object connString - URI or session name. user

PostgreSQL version 10.2 or higher and TimescaleDB version 1.5 or higher for all Zabbix tables that are managed by TimescaleDB. During the upgrade or migration to TimescaleDB, initial compression of the large setupfor more information. Items VMware cluster performance counters A new vmware.cl.perfcounter[,,,] item allows to retrieve VMware cluster performance counter metrics. JMX items allows to define and execute transformation rules for the received item values. Preprocessing is managed by a preprocessing manager process, which was added in Zabbix 3.4, along with preprocessing workers

functionality is implemented for custom graphs and ad-hoc graphs. • Multi-select fields can be managed by a screen reader. Readable summary in maps A hidden ”aria-label” property has been added to maps Parameters Comments vmware.cluster.discovery[] Discovery of VMware clusters. JSON object url - VMware service URL vmware.cluster.status[, ] VMware cluster status. Integer: 0 - gray; gray; 1 - green; 2 - yellow; 3 - red url - VMware service URL name - VMware cluster name vmware.datastore.discovery[] 251 Key Discovery of VMware datastores. JSON object url - VMware

Parameters Comments vmware.cluster.discovery[] Discovery of VMware clusters. JSON object url - VMware service URL vmware.cluster.status[, ] VMware cluster status. Integer: 0 - gray; VMware cluster name vmware.eventlog[] VMware event log. Log url - VMware service URL vmware.fullname[] VMware service full name. String url - VMware service URL vmware.hv.cluster.name[ name[,] VMware hypervisor cluster name. String url - VMware service URL uuid - VMware hypervisor host name vmware.hv.cpu.usage[,] VMware hypervisor processor usage (Hz)