Hello,
I've set up my Zabbix environment with one server and two proxies, all running version 2.2.3. I got few problems with proxies, so I hope someone could help me a bit.
1) Queue: All 3 hosts (server and proxies) show the same number for the internal item with key zabbix[queue,10m]. Queue is actually on one proxy, because there are some network devices down from time to time, but as the item shows the same number for each host, I have 3 different triggers showing like the problem is appearing on server and other proxy too. So how to avoid this item showing overall queue and just to show the number of queued items on the current host (server or one of the proxies etc)?
2) Events when a proxy is down
Maybe a pseudoproblem, but.. Problem starts when the server loses contact with a proxy, then proxy continues collecting data and saving that til connection is restored (or for the configured number of hours in parameter ProxyOfflineBuffer). The problem is that as we cannot see the realtime events collected by the proxy, we are not taking any actions until the connection is restored. Now when the connection is restored, all the collected data is sent from proxy to server. This causes lots of triggers being activated at once showing all the triggers that had problems during the downtime. As some/all of the things may have been repaired already, we get the info with a delay. How to avoid triggers to light up when the problem is already fixed before connection between proxy and server is restored?
Raido
I've set up my Zabbix environment with one server and two proxies, all running version 2.2.3. I got few problems with proxies, so I hope someone could help me a bit.
1) Queue: All 3 hosts (server and proxies) show the same number for the internal item with key zabbix[queue,10m]. Queue is actually on one proxy, because there are some network devices down from time to time, but as the item shows the same number for each host, I have 3 different triggers showing like the problem is appearing on server and other proxy too. So how to avoid this item showing overall queue and just to show the number of queued items on the current host (server or one of the proxies etc)?
2) Events when a proxy is down
Maybe a pseudoproblem, but.. Problem starts when the server loses contact with a proxy, then proxy continues collecting data and saving that til connection is restored (or for the configured number of hours in parameter ProxyOfflineBuffer). The problem is that as we cannot see the realtime events collected by the proxy, we are not taking any actions until the connection is restored. Now when the connection is restored, all the collected data is sent from proxy to server. This causes lots of triggers being activated at once showing all the triggers that had problems during the downtime. As some/all of the things may have been repaired already, we get the info with a delay. How to avoid triggers to light up when the problem is already fixed before connection between proxy and server is restored?
Raido
Comment