nodata-based trigger going off at the wrong time
OS: Ubuntu Server 11.04
Zabbix version: 1.8.3-2ubuntu1 (the default version)
Ok, here's the thing: all morning the "Server Whatever is unreachable" trigger, which i modified to "agent.ping.nodata(180)" as "status" seems to be deprecated, has been going off on random hosts. When you check the overview, it shows that the server is in fact up, that the "500 last values" are "Up(1)" and that the server is reachable. Yet even the overview shows it in red:
And of course, the server maps are all going Chicken Little on this despite everything being fine.
I went to the template and changed the trigger to check the last 300 seconds instead of 180, with no difference (what difference could there be if all the data is in fact there anyway?).
Is it a known bug, something i'm doing wrong or something else?
Zabbix version: 1.8.3-2ubuntu1 (the default version)
Ok, here's the thing: all morning the "Server Whatever is unreachable" trigger, which i modified to "agent.ping.nodata(180)" as "status" seems to be deprecated, has been going off on random hosts. When you check the overview, it shows that the server is in fact up, that the "500 last values" are "Up(1)" and that the server is reachable. Yet even the overview shows it in red:
And of course, the server maps are all going Chicken Little on this despite everything being fine.
I went to the template and changed the trigger to check the last 300 seconds instead of 180, with no difference (what difference could there be if all the data is in fact there anyway?).
Is it a known bug, something i'm doing wrong or something else?