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.

-

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.

+

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.