-
Incident report
-
Resolution: Won't fix
-
Major
-
None
-
1.8.3
-
Three nodes set up as children of a single node, all monitoring the same systems from different geographical locations. All systems are running RHEL5 with Zabbix 1.8.3.
When triggers are set, they show up in the master node under ALL, but they appear in an Acknowledged state. Since they show up as being ack'd already. Alerts set on the master node are executed, but they cannot be stopped. Setting a condition in an alert of "Event acknowledged = "Not Ack" " is rendered useless. The only way to stop alerts is to go to the child node and ack the trigger.