Hi,
I have hosts in two datacenters. Zabbix is on one datacenter, lets call it DC "A". For all hosts in A I have trigger dependencies ICMP Ping <- SNMP Generic <- Rest of SNMP.
So if the host does not ping, all SNMP Generic does not alert. If SNMP Generic fails, all other SNMP stuff does not alert.
Now I have datacenter "B". If want to add "router B" to my dependency chain. So if router B is not available, no triggers for the hosts in DC B will fire.
How do I solve this problem?
Of course, I could have a new "Template ICMP Ping B" for all hosts in DC B, that would imply a new "Template SNMP Generic B" where the trigger depends on "Template ICMP Ping B", and also a whole new set of SNMP templates, that depend on SNMP Generic B. This makes no sense.
Is there any chance to solve this problem, i.e. using macro names or host groups for the decision which of a parent router status is important?
Michael.
I have hosts in two datacenters. Zabbix is on one datacenter, lets call it DC "A". For all hosts in A I have trigger dependencies ICMP Ping <- SNMP Generic <- Rest of SNMP.
So if the host does not ping, all SNMP Generic does not alert. If SNMP Generic fails, all other SNMP stuff does not alert.
Now I have datacenter "B". If want to add "router B" to my dependency chain. So if router B is not available, no triggers for the hosts in DC B will fire.
How do I solve this problem?
Of course, I could have a new "Template ICMP Ping B" for all hosts in DC B, that would imply a new "Template SNMP Generic B" where the trigger depends on "Template ICMP Ping B", and also a whole new set of SNMP templates, that depend on SNMP Generic B. This makes no sense.
Is there any chance to solve this problem, i.e. using macro names or host groups for the decision which of a parent router status is important?
Michael.