Eliminate a plethora of alerts from a dependent chain of devices

[gherbstman]

We have been using dependencies on triggers to eliminate huge numbers of alerts for some time with great success. An example may be a network router with 100 devices behind it. If the router goes down I do not want to see 100 additional alerts for all the dependent items.

Version 6 has me perplexed on how to accomplish this. Is this an oversight on the removal of dependencies or am I missing an alternative method to accomplish it?

One of my thoughts is to create a macro in the template and base the trigger on a macro value if populated. The value would point to a parent item.

If that sounds like a viable option, can someone give me some tips on how to write the icmp lost trigger to include a macro item only if it is populated?

[cyber]

Interesting.. at least docs about trigger dependencies are identical for 6 and 5 and 4 ... almost word by word exact same... So how can behavior be different? Go to trigger config, dependencies tab and add a dependency... ?
Unfortunately I have no v6 at hand....

EDIT... ah I reached that upgrade note...

Changing dependency for inherited triggers disabled


The possibility to change dependencies for triggers inherited from a template is now disabled. The reason is that upon updating the dependencies of a template trigger, the dependencies of inherited triggers are overwritten. Thus it is more reliable always to set trigger dependencies only on the root template level.

That seems a bit weird... working against host to host dependencies... And that is the main reason people use it... hmmmm
They assume there are dependencies already in template... but if there's none? Ugh...

[tim.mooney]

I don't fully understand what they're saying in their explanation of why they changed it, but this change has me concerned. We use multiple different templates for some hosts, and we have trigger dependencies between the templates.

I really hope this change doesn't cause us major issues when we eventually upgrade to 6.0.x

[gherbstman]

Here are links to Zabbix issue tickets to vote on.

https://support.zabbix.com/browse/ZBX-20689?jql=summary%20~%20%22depend*%22%20OR%20description%20~%20%22depend*%22%20ORDER%20BY%20created%20DESC%2C%20lastViewed%20DESC

https://support.zabbix.com/browse/ZBX-20613?jql=summary%20~%20%22depend*%22%20OR%20description%20~%20%22depend*%22%20ORDER%20BY%20created%20DESC%2C%20lastViewed%20DESC

[fransyk]

We have been using dependencies on triggers to eliminate huge numbers of alerts for some time with great success. An example may be a network router with 100 devices behind it. If the router goes down I do not want to see 100 additional alerts for all the dependent items.

Version 6 has me perplexed on how to accomplish this. Is this an oversight on the removal of dependencies or am I missing an alternative method to accomplish it?

One of my thoughts is to create a macro in the template and base the trigger on a macro value if populated. The value would point to a parent item.

If that sounds like a viable option, can someone give me some tips on how to write the icmp lost trigger to include a macro item only if it is populated?

Same problem for me. It was so handy to be able to create dependencies between hosts and now it doesn't work anymore. Maybe I'm going back to version 5.0