status. ha_remove_node=target Remove the high availability (HA) node specified by its name or ID. Note that active/standby nodes cannot be removed. target - name or ID of the node (can be obtained 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 for each each Zabbix server that will be an HA cluster node. This is a unique node identifier (e.g. zabbix-node-01) that the server will be referred to in agent and proxy configurations. If you do not specify

status. ha_remove_node=target Remove the high availability (HA) node specified by its name or ID. Note that active/standby nodes cannot be removed. target - name or ID of the node (can be obtained 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 for each each Zabbix server that will be an HA cluster node. This is a unique node identifier (e.g. zabbix-node-01) that the server will be referred to in agent and proxy configurations. If you do not specify

status. ha_remove_node=target Remove the high availability (HA) node specified by its name or ID. Note that active/standby nodes cannot be removed. target - name or ID of the node (can be obtained availability Starting Zabbix server as cluster node 30 Two parameters are required in the server configuration to start a Zabbix server as cluster node: • HANodeName parameter must be specified for for each Zabbix server that will be an HA cluster node. This is a unique node identifier (e.g. zabbix-node-01) that the server will be referred to in agent and proxy configurations. If you do not specify

zabbix_server instances or nodes, where only one node can be active (working) at a time, while other nodes are on standby, ready to take over in case the current node is stopped or fails. See also: High availability now printed to the console. • It is possible to send longer input parameters, such as HA node name instead of node number. Runtime controls on BSD-based OS 15 Previously, Zabbix server and Zabbix proxy CockroachDB by HTTP • Envoy Proxy by HTTP • HashiCorp Consul Cluster by HTTP • HashiCorp Consul Node by HTTP See setup instructions for HTTP templates. You can get these templates: • In Configuration

HTTP - native template to monitor Elasticsearch. ClickHouse • Template DB ClickHouse - collects node metrics from ClickHouse HTTP interface using HTTP agent. (see description). Memcached • Template 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. You can get these templates: database instance or an external one. • Zabbix agent - a Zabbix agent can be deployed on each available node for stability and performance monitoring on remote nodes. It allows to gather metrics with full automation

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. NetApp NetApp AFF A700 by 4 Zabbix 3.0 Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Node-based distributed monitoring removed 93 Upgrade from Read full upgrade notes Most important changes MongoDB cluster by Zabbix agent 2 - see setup instructions for Zabbix agent 2 templates; • MongoDB node by Zabbix agent 2 - see setup instructions for Zabbix agent 2 templates; • NetApp AFF A700 by HTTP

0 Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Node-based distributed monitoring removed 2.0.x For: Zabbix 2.2 Zabbix 2.4 Zabbix 3.0 Zabbix 3.2 separated with dots. A segment can be either a simple word like a JSON value name, * or a more complex construct enclosed within square brackets [ ]. The separating dot before bracket segment is optional and See also: Escaping special characters from LLD macro values in JSONPath. Supported segments Segment Description Match object property by name. * Match all object properties. [''] Match

Zabbix agent, which should be imported/updated first • Template OS Linux by Prom - Linux monitored via node exporter (monolithic) • Template OS Linux SNMPv2 - Linux monitored via SNMPv2 (modular) – depends App RabbitMQ node by Zabbix agent - collect metrics by polling RabbitMQ management plugin with Zabbix agent locally; • Template App RabbitMQ cluster by HTTP and Template App RabbitMQ node by HTTP - collect 2.x LTS For: Zabbix 2.4 Zabbix 3.0 Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Node-based distributed monitoring removed 2.0.x For: Zabbix 2.2 Zabbix 2.4 Zabbix 3.0 Zabbix 3.2

PHP version upped from 5.3.0 to 5.4.0 LogFile agent parameter must be specified 2.2.x Also for 2.4 Node-based distributed monitoring removed 2.0.x Also for 2.2 Minimum required PHP version upped from 5 in XML format. Macros can be used as a text node, attribute or CDATA section. Values from macros are resolved and then escaped automatically in a text node and attribute. If ”Content-Type” is not specified may look like: Service | |-Workstations | | | |-Workstation1 | | | |-Workstation2 | |-Servers Each node of the structure has attribute status. The status is calculated and propagated to upper levels according

specified 2.2.x LTS For: Zabbix 2.4 Zabbix 3.0 Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Node-based distributed monitoring removed 2.0.x For: Zabbix 2.2 Zabbix 2.4 Zabbix 3.0 Zabbix 3.2 in XML format. Macros can be used as a text node, attribute or CDATA section. Values from macros are resolved and then escaped automatically in a text node and attribute. If ”Content-Type” is not specified may look like: Service | |-Workstations | | | |-Workstation1 | | | |-Workstation2 | |-Servers Each node of the structure has attribute status. The status is calculated and propagated to upper levels according