This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
manual:config:triggers:dependencies [2017/02/16 13:42] viktors.tjarve [Overview] improved description of the dependent trigger behavior |
manual:config:triggers:dependencies [2019/04/02 06:04] (current) |
||
---|---|---|---|
Line 13: | Line 13: | ||
If both the server and the router are down and dependency is there, Zabbix will not execute actions for the dependent trigger. | If both the server and the router are down and dependency is there, Zabbix will not execute actions for the dependent trigger. | ||
- | Actions on dependent triggers will not be executed if the state of the trigger that it depends on changes from 'PROBLEM' to 'UNKNOWN'. | + | Actions on dependent triggers will not be executed if the trigger they depend on: |
+ | |||
+ | * changes its state from 'PROBLEM' to 'UNKNOWN' | ||
+ | * is closed manually, by correlation or with the help of time- based functions | ||
+ | * is resolved by a value of an item not involved in dependent trigger | ||
+ | * is disabled, has disabled item or disabled item host | ||
+ | |||
+ | Note that "secondary" (dependent) trigger in the above-mentioned cases will not be immediately updated. | ||
- | It is important to note that events/actions for dependent triggers will not be suppressed if the trigger they depend on is disabled, has disabled item or disabled item host. | ||
Also: | Also: |