Trigger dependancy in Actions
Hi guys, I hope this doesn't become too long winded but I am having an issue with the way Zabbix is sending actions based on triggers..
First here is my basic network layout.. I monitor alot of remote sites all of which are fairly small but also fairly critical.. I am trying to ensure that if an 'action' email is sent out (to third party) from Zabbix that it is only sent in the event that the particular site/device is down, not if lower level sites/devices are down.. Here is what I mean .. Zabbix Server -> Sonicwall -> Sonicwall -> -> Sonicwall -> PLC device/Workstation. (yes the cascading is correct)
So from the above scenario when I loose connectivity to the first sonicwall I don't want to be notified(via email) of a loss of connectivity to the subsequent connections below it..
In the web UI I am able to define trigger dependancies which appear to work as expected.. There is sometimes a brief display that multiple sonicwalls are down but after the trigger period expires twice I only see the top level issue which is what I want..
The problem arises with the email notification or action as Zabbix labels it.. Since the lower level trigger happened to fire first it set the trigger state to problem.. Then when the upper level trigger goes to problem zabbix somehow just ignores (in the web) the state of the trigger.. However the Action does not ignore this it sees it as a problem state and fires off 2 emails(or several in reality).. This is however a bit randdom since if Zabbix happens to check the upper level sonicwall it will immediately ignore the lower level triggers and never set it to problem..
Sorry for the long winded explanation but I want to be clear.. Does anyone know of a better way to accomplish what I am doing? I have been suggested to adjust timing of triggers but I am using a template for all my sonicwalls and believe it would make a mess to have 3 different sonicwall templates with different timings to accomplish this..
First here is my basic network layout.. I monitor alot of remote sites all of which are fairly small but also fairly critical.. I am trying to ensure that if an 'action' email is sent out (to third party) from Zabbix that it is only sent in the event that the particular site/device is down, not if lower level sites/devices are down.. Here is what I mean .. Zabbix Server -> Sonicwall -> Sonicwall -> -> Sonicwall -> PLC device/Workstation. (yes the cascading is correct)
So from the above scenario when I loose connectivity to the first sonicwall I don't want to be notified(via email) of a loss of connectivity to the subsequent connections below it..
In the web UI I am able to define trigger dependancies which appear to work as expected.. There is sometimes a brief display that multiple sonicwalls are down but after the trigger period expires twice I only see the top level issue which is what I want..
The problem arises with the email notification or action as Zabbix labels it.. Since the lower level trigger happened to fire first it set the trigger state to problem.. Then when the upper level trigger goes to problem zabbix somehow just ignores (in the web) the state of the trigger.. However the Action does not ignore this it sees it as a problem state and fires off 2 emails(or several in reality).. This is however a bit randdom since if Zabbix happens to check the upper level sonicwall it will immediately ignore the lower level triggers and never set it to problem..
Sorry for the long winded explanation but I want to be clear.. Does anyone know of a better way to accomplish what I am doing? I have been suggested to adjust timing of triggers but I am using a template for all my sonicwalls and believe it would make a mess to have 3 different sonicwall templates with different timings to accomplish this..