Actions fire for wrong hosts/confitions
It seems that after our upgrade from 1.8 to 2.0 Zabbix is firing actions 1.) for the wrong hosts and 2.) at the wrong severities.
Let me explain that a little more.
There is a user FOO that has rad-only permissions to host ABC.
There is also a host XYZ that he has no permission at all for.
And there is an action that is constrained to only fire if trigger severity = Desaster and will notify user FOO.
So to my understanding this notification is only supposed to be sent out to user FOO if the trigger severity = Desaster and the user has at least read-only access to the host.
So triggers for host XYZ should not be sent to user ABC even if they are severity = Desaster since he/she has no permission for the host.
But what actually happens is that user FOO is notified via this action 1.) if triggers on host XYZ fire and 2.) if the severity = Information.
And if that wan't enough of bad things happening this does not happen all the time - seems randomly.
So for some reason zabbix does sometimes neither honor that the user FOO has no permissions to host XYZ nor that the action constraint is Severity = Desaster only.
Also strange is that only the trigger change from OK -> PROBLEM is causing the action to fire for user FOO and host XYZ but the recovery event from PROBLEM -> OK is not. At least not for host XYZ.
For host ABC the initial event as well as the recovery action is sent as intended.
So it seems that there is a issue somewhere in the code that descided when to execute and action for a users?
Anybody with similar issues?
Thanks, Thorsten
Let me explain that a little more.
There is a user FOO that has rad-only permissions to host ABC.
There is also a host XYZ that he has no permission at all for.
And there is an action that is constrained to only fire if trigger severity = Desaster and will notify user FOO.
So to my understanding this notification is only supposed to be sent out to user FOO if the trigger severity = Desaster and the user has at least read-only access to the host.
So triggers for host XYZ should not be sent to user ABC even if they are severity = Desaster since he/she has no permission for the host.
But what actually happens is that user FOO is notified via this action 1.) if triggers on host XYZ fire and 2.) if the severity = Information.
And if that wan't enough of bad things happening this does not happen all the time - seems randomly.
So for some reason zabbix does sometimes neither honor that the user FOO has no permissions to host XYZ nor that the action constraint is Severity = Desaster only.
Also strange is that only the trigger change from OK -> PROBLEM is causing the action to fire for user FOO and host XYZ but the recovery event from PROBLEM -> OK is not. At least not for host XYZ.
For host ABC the initial event as well as the recovery action is sent as intended.
So it seems that there is a issue somewhere in the code that descided when to execute and action for a users?
Anybody with similar issues?
Thanks, Thorsten