In the Zabbix 2.4 manual about trigger dependencies
Will be nice - and much more convenient - if Zabbix dependencies had conditional options.
Real life scenario.
I have 1 front-end (working as balancer) and 2 jboss server in managed as "cluster".
Front-end: 1 web page monitored (http://front-end/webapplication)
Jboss01: 1 web page monitored (http://jboss01/webapplication)
Jboss02: 1 web page monitored (http://jboss02/webapplication)
Each one monitored in Zabbix.
So, if url in jboss01 and jboss03 are down, front-end is down.
if url in jboss01 or jboss03 are down, front-end is up.
if url in front-end is down, don't means jboss01 and/or jboss02 are down.
If the dependencies have a conditional parameter.
Eg.
Trigger: FRONT-END url is down because all cluster nodes are down
Dependencies: JBOSS01 and JBOSS02
Or
Eg.
Trigger: FRONT-END url is up but working in half os capacibility
Dependencies: JBOSS01 OR JBOSS02
Sorry for the bad English.
Code:
[I]If found, and one of those triggers is in 'Problem' state, then the trigger status will not be changed and thus actions will not be executed and notifications will not be sent.[/I]
Real life scenario.
I have 1 front-end (working as balancer) and 2 jboss server in managed as "cluster".
Front-end: 1 web page monitored (http://front-end/webapplication)
Jboss01: 1 web page monitored (http://jboss01/webapplication)
Jboss02: 1 web page monitored (http://jboss02/webapplication)
Each one monitored in Zabbix.
So, if url in jboss01 and jboss03 are down, front-end is down.
if url in jboss01 or jboss03 are down, front-end is up.
if url in front-end is down, don't means jboss01 and/or jboss02 are down.
If the dependencies have a conditional parameter.
Eg.
Trigger: FRONT-END url is down because all cluster nodes are down
Dependencies: JBOSS01 and JBOSS02
Or
Eg.
Trigger: FRONT-END url is up but working in half os capacibility
Dependencies: JBOSS01 OR JBOSS02
Sorry for the bad English.
Comment