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/11/21 12:59] natalja.cernohajeva |
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: |
- | "Secondary" (dependent) trigger will update its state correctly if it depends on the same item which resolves "Main" trigger. If "Main" trigger resolves by other means, for example: | + | * 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 | ||
- | * manually closed; | + | Note that "secondary" (dependent) trigger in the above-mentioned cases will not be immediately updated. |
- | * by global correlation; | + | |
- | * with the help of time-based functions; | + | |
- | * a value of an item not involved in "secondary" (dependent) trigger | + | |
- | * becomes UNKNOWN | + | |
- | * gets disabled itself or any of it's items get disabled | + | |
- | "Secondary" (dependent) trigger will not be immediately updated leading to various sorts of confusion. | ||
- | |||
- | 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: |