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

checks are picked up and performed by the discovery workers. Only those checks that have the same IP and port are scheduled sequentially because some devices may not allow concurrent connections on the 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

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

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

DNS}, {#VM.GUESTFAMILY}, {#VM.GUESTFULLNAME}, {#VM.IP}; • vmware.hv.discovery item, used for hypervisor discovery, now returns an additional field {#HV.IP}. 15 8 What’s new in Zabbix 5.2.3 Items A new 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

setupfor more information. Items VMware cluster performance counters A new vmware.cl.perfcounter[,,,] item allows to retrieve VMware cluster performance counter metrics. JMX items New templates These templates are now available for out-of-the-box monitoring: • Big-IP SNMP - monitoring of BIG-IP application services; • GridGain by JMX - see setup instructions for JMX templates; to Zabbix agent 2. These items, used with Zabbix agent 2, now support concurrent check processing. IP selection priority during VMware hypervisor discovery To ensure predictable discovery of interface

New official templates are available for monitoring: Elasticsearch • Template App Elasticsearch Cluster by HTTP - native template to monitor Elasticsearch. ClickHouse • Template DB ClickHouse - collects will be removed (note that history of the deleted items will be lost). Items • The zabbix[stats,<ip>,] internal item now also returns version of Zabbix server or Zabbix proxy • A new zabbix[version] logged into an Audit log with the following details: • Timestamp • User that started a script • IP of the target host or Zabbix server/proxy • Script after macros substitution (secret macros will be

• 添加了对监控项 net.dns 和 net.dns.record 的原生支持。这些监控项与 Zabbix agent 2 一起使用，现在支持并发检查处理。在 Windows 上，ip 参数中允许自定义 DNS IP 地址，timeout 和 count 参数不再被忽略。 • S.M.A.R.T. 插件支持的 smart.disk.discovery 和 smart.attribute.discovery Zabbix 6.0.5 新功能 模板 新的模板已经可以使用: • CockroachDB by HTTP • Envoy Proxy by HTTP • HashiCorp Consul Cluster by HTTP • HashiCorp Consul Node by HTTP 有关设置说明，请参阅HTTP 模板. 你可以使用如下方式获取到新的模板: • 在新安装的 配置 → 模板中; website. 25 What’s new in Zabbix 6.0.20 Templates A new template AWS ECS Cluster by HTTP (along with its Serverless Cluster version) is available. You can get this template: • In Configuration → Templates

个新的发现管理器进程，以及可配置数量的发现工作进 程（或线程）。 发现管理器处理发现规则，并为每个规则创建一个包含任务（服务检查）的发现作业。服务检查由发现工作进程接收并执行。只有那些具 有相同 IP 和端口的检查才会按顺序进行调度，因为某些设备可能不允许在相同端口上进行并发连接。 一个新的内部监控项 zabbix[discovery_queue] 允许监视队列中的发现检查的数量。 Star 参数必须为每个节点指定。 NodeAddress 参数 (address:port) 将被 Zabbix 前端用来连接到主 server 节点。NodeAddress 必须匹配相应 Zabbix server 的 IP 或 FQDN 名称。 在对配置文件进行更改后，重新启动所有 Zabbix server。- 它们现在将作为集群节点启动。- server 的新状态可以在 报表 → 系统信息 查 看，也可以用以下命令查看: 分钟之间；支持时间后缀，例如 10s、1m） 可以监控节点状态： • ·在报告 → 系统信息 • ·在系统信息仪表板小部件中 • ·使用服务器的 ha_status 运行时控制选项（见上文）。 zabbix[cluster,discovery,nodes] 内部监控项可用于节点发现，因为它返回具有高可用性节点信息的 JSON。 禁用 HA 集群 禁用 HA 高可用集群: • 备份配置文件 • 停止 standby

different proxies will be always treated as different hosts. This allows to perform discovery on the same IP ranges used by different subnets. 5.21 Items 5.21.1 Database monitoring is now official ODBC monitoring now also supported in trigger descriptions: {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {ITEM.VALUE}, {ITEM.LASTVALUE} and {$MACRO}. These macros will be expanded when viewing the trigger will now also expand host name macros - {HOST.HOST}, {HOST.NAME} and host connection macros - {HOST.IP}, {HOST.DNS}, {HOST.CONN}. 5.23.6 User macros in allowed hosts 17 User macros are now supported