Hello,
according to the manual trigger dependencies should behave like this (v1.6, page 84):
"A trigger may have list of one or more triggers it depends on. It means that the trigger will still change its status regardless of state of the triggers in the list, yet the trigger won’t generate notifications and actions in case if one of the trigger in the list has state TRUE."
I'm testing dependencies on the nightly build version 1.5 and experiencing quite strange behavior. Here is the scenario:
1. I used following triggers from Template_Linux:
- WEB (HTTP) server is down on {HOSTNAME}
- Apache is not running on {HOSTNAME}.
2. I defined following dependency:
"WEB (HTTP) server is down on {HOSTNAME}" depends on "Apache is not running on {HOSTNAME}".
3. I defined mail sending action for trigger "WEB (HTTP) server is down on {HOSTNAME}".
4. After crashing the apache on defined host following happened:
- Contrary to the manual action was performed and I received the notification.
- On Dashboard and Monitoring/Triggers interfaces trigger "WEB (HTTP) server is down on {HOSTNAME}" was not displayed at all and I didn't manage to find something like "show dependent triggers" switch. This behavior is not bad, but slightly confusing and should be definitely documented somewhere.
- Trigger "WEB (HTTP) server is down on {HOSTNAME}" is correctly displayed on Overview and Events interfaces.
Does anyone see error in my configuration or is this a Zabbix issue?
Thanks in advance,
emir
according to the manual trigger dependencies should behave like this (v1.6, page 84):
"A trigger may have list of one or more triggers it depends on. It means that the trigger will still change its status regardless of state of the triggers in the list, yet the trigger won’t generate notifications and actions in case if one of the trigger in the list has state TRUE."
I'm testing dependencies on the nightly build version 1.5 and experiencing quite strange behavior. Here is the scenario:
1. I used following triggers from Template_Linux:
- WEB (HTTP) server is down on {HOSTNAME}
- Apache is not running on {HOSTNAME}.
2. I defined following dependency:
"WEB (HTTP) server is down on {HOSTNAME}" depends on "Apache is not running on {HOSTNAME}".
3. I defined mail sending action for trigger "WEB (HTTP) server is down on {HOSTNAME}".
4. After crashing the apache on defined host following happened:
- Contrary to the manual action was performed and I received the notification.
- On Dashboard and Monitoring/Triggers interfaces trigger "WEB (HTTP) server is down on {HOSTNAME}" was not displayed at all and I didn't manage to find something like "show dependent triggers" switch. This behavior is not bad, but slightly confusing and should be definitely documented somewhere.
- Trigger "WEB (HTTP) server is down on {HOSTNAME}" is correctly displayed on Overview and Events interfaces.
Does anyone see error in my configuration or is this a Zabbix issue?
Thanks in advance,
emir