PATCH: Preliminary Multiple Zabbix Servers

[James Wells]

Greetings,

Below is a very very preliminary patch that allows you to implement multiple Zabbix servers against a single database. With this patch, you can have anywhere from a single Zabbix server, up to 255 distinct Zabbix servers using a single database. Each server will only monitor the items specific to their "zone".

Each server must be assigned a unique integer in the zabbix_server.conf conf and then the serverid field in the items table needs to be populated with the ID of the server you wish to monitor that item. The conf file entry looks like;

# This defines which server this is.
# Default value 1
# This parameter must be between 1 and 255
Server=1

Please note that this patch is very very preliminary and has had very minimal testing. Use at your own risk. Also note that I have not yet had time to implement the frontend to manage this just yet.

EDIT: 14 Sep 05 -- Posted an updated patch against the latest CVS code.

[James Wells]

Okay, I finally had time to finish the basic UI functionality to support multiple servers. There is no real error checking in place yet, but it is functional

I have only been able to test this with three servers, with server A monitoring server B, and server B monitoring server C, and server C monitoring server A. All three servers use the same database and are alerting only for the items they are monitoring.

Additionally, I tested Zabbix Agents active under this configuration and they worked correctly.

Next version of the patch, I hope to have the servers be able to respond to Zabbix Agent active queries to reconfigure the the Agent to use a different server. With this change, the Agent will contact the first server listed in it's config for a list of active items, however, the server will also be able to tell the Agent which server to send the item information to on a per item basis.

NOTE: The patch is zip compressed and attached below.