Zabbix multi-server configuration¶

The Zabbix multi-server configuration involves configuring the Zabbix agent (zabbix_agentd) to accept connections and report Metrics to multiple Zabbix server or proxy instances.^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md]

Configuration¶

To enable multi-server support, the Server parameter in the zabbix_agentd.conf configuration file must be modified. This parameter accepts a comma-separated list of IP addresses or hostnames^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].

Server=zabbix.mypay1.com,10.140.0.23

This configuration allows the agent to process requests from both the primary server (e.g., zabbix.mypay1.com) and a secondary server or proxy (e.g., 10.140.0.23)^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].

Deployment Procedure¶

A typical deployment procedure on a Linux system involves backing up the existing configuration and using sed to append the new server address^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md]:

cp /etc/zabbix/zabbix_agentd.conf /etc/zabbix/zabbix_agentd.conf.bak
sed -i 's/Server=zabbix.mypay1.com/Server=zabbix.mypay1.com,10.140.0.23/g' /etc/zabbix/zabbix_agentd.conf
systemctl restart zabbix-agent.service
systemctl status zabbix-agent.service

Related Concepts¶

• [[Zabbix]]
• [[Monitoring]]
• [[Active vs. Passive checks]]

Sources¶

^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md]