Zabbix Documentation 4.0

3.04.04.24.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.4Guidelines

User Tools

Site Tools


manual:config:triggers:dependencies

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:config:triggers:dependencies [2014/09/30 12:54]
127.0.0.1 external edit
manual:config:triggers:dependencies [2017/12/01 14:15] (current)
natalja.cernohajeva Updated info about actions on dependent trigger non-execution
Line 9: Line 9:
 While Zabbix does not support dependencies between hosts directly, they may be defined with another, more flexible method - trigger dependencies. A trigger may have one or more triggers it depends on. While Zabbix does not support dependencies between hosts directly, they may be defined with another, more flexible method - trigger dependencies. A trigger may have one or more triggers it depends on.
  
-So in our simple example we open the server trigger configuration form and set that it depends on the respective trigger of the router. With such dependency the server trigger will not change state as long as the trigger it depends on is in 'Problem' state - and thus no dependant actions will be taken and no notifications sent.+So in our simple example we open the server trigger configuration form and set that it depends on the respective trigger of the router. With such dependency the server trigger will not change state as long as the trigger it depends on is in 'PROBLEM' state - and thus no dependant actions will be taken and no notifications sent.
  
 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 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. ​
 +
  
 Also: Also:
Line 19: Line 29:
   * Trigger dependency may be added from template trigger to a host trigger. In this case, linking such a template to a host will create a host trigger that depends on the same trigger template trigger was depending on. This allows to, for example, have a template where some triggers depend on router (host) triggers. All hosts linked to this template will depend on that specific router.   * Trigger dependency may be added from template trigger to a host trigger. In this case, linking such a template to a host will create a host trigger that depends on the same trigger template trigger was depending on. This allows to, for example, have a template where some triggers depend on router (host) triggers. All hosts linked to this template will depend on that specific router.
   * Trigger dependency from a host trigger to a template trigger may not be added.   * Trigger dependency from a host trigger to a template trigger may not be added.
 +  * Trigger dependency may be added from a trigger prototype to another trigger prototype (within the same low-level discovery rule) or a real trigger. A trigger prototype may not depend on a trigger prototype from a different LLD rule or on a trigger created from trigger prototype. Host trigger prototype cannot depend on a trigger from a template.
  
 === Configuration === === Configuration ===