As part of our monitoring solution we have two Zabbix Monitoring Servers in different regions.
Each region's Monitoring Server exclusively monitors Hosts in its' own region however every individual Host is configured to receive monitoring checks from both Servers. See below:
This means in the event of a Zabbix Monitoring Server failure we can easily configure the other Zabbix Monitoring Server to check Hosts in both regions.
The downside of this configuration however is that Hosts are expecting Active Checks to be sent from both Monitoring Servers however these Servers are not always configured with both region's Hosts (unnecessary data collection/network traffic/etc.)
This results in the logs being flooded as follows:
Monitoring Server Region 1
Host 3 Region 2
Any thoughts on suppressing this log spam?
Each region's Monitoring Server exclusively monitors Hosts in its' own region however every individual Host is configured to receive monitoring checks from both Servers. See below:
Code:
Server=MonServer1, MonServer2 ServerActive=MonServer1, MonServer2
The downside of this configuration however is that Hosts are expecting Active Checks to be sent from both Monitoring Servers however these Servers are not always configured with both region's Hosts (unnecessary data collection/network traffic/etc.)
This results in the logs being flooded as follows:
Monitoring Server Region 1
Code:
1954:20171119:031922.419 cannot send list of active checks to "192.xxx.xxx.xx1": host [Host1Region2] not found 1954:20171119:031922.747 cannot send list of active checks to "192.xxx.xxx.xx2": host [Host2Region2] not found 1954:20171119:031934.781 cannot send list of active checks to "192.xxx.xxx.xx3": host [Host3Region2] not found
Code:
1954:20171119:031934.781 no active checks on server [MonServer1Region1:10051]: host [Host3Region2] not found