Hi,
We're running Zabbix version 2.4.8 (I know it's old, we're testing and planning the upgrade to 3.4 at the moment).
We have issues with a few of our triggers. The one that's mostly causing problems is monitoring the queue length and fires when the queue get's too long. The item is defined as follows:
It's correctly collecting data:
As you can see in the screenshot during the night the threshold for the trigger was reached 3 times and the trigger also fired accordingly, see Event-history:
Now the problem, as you can see, is that the trigger didn't fall back to the OK-State after the last status change at about 5:22 AM this morning.
We do occasionally have the same problem with other hostss that are monitored by one of our zabbix-proxies. Zabbix says the host is unavailable by ICMP but we can pin the host from the zabbix-proxy without any problem, and the ICMP-item that collects the data also says that the host is reachable, but the trigger never goes back in the OK state. We found a workaround for this problem by changing the IP-address of the host to a random IP which does not exist and then change it back later. But this is certainly no ideal solution.
Does anybody have any expericences with this problem?
We're running Zabbix version 2.4.8 (I know it's old, we're testing and planning the upgrade to 3.4 at the moment).
We have issues with a few of our triggers. The one that's mostly causing problems is monitoring the queue length and fires when the queue get's too long. The item is defined as follows:
It's correctly collecting data:
As you can see in the screenshot during the night the threshold for the trigger was reached 3 times and the trigger also fired accordingly, see Event-history:
Now the problem, as you can see, is that the trigger didn't fall back to the OK-State after the last status change at about 5:22 AM this morning.
We do occasionally have the same problem with other hostss that are monitored by one of our zabbix-proxies. Zabbix says the host is unavailable by ICMP but we can pin the host from the zabbix-proxy without any problem, and the ICMP-item that collects the data also says that the host is reachable, but the trigger never goes back in the OK state. We found a workaround for this problem by changing the IP-address of the host to a random IP which does not exist and then change it back later. But this is certainly no ideal solution.
Does anybody have any expericences with this problem?
Comment