Host based dependancies

[louis-m]

I'm struggling with the sheer weight of dependancies and some may say that's down to a poor layout of triggers etc.
However, I think it would be a really good idea if a host could be given a dependancy on another trigger
eg a switch sits behind a router. Rather than have to configure all of the dependancies on the templates etc, you simply configure the switch (at host level) to have a dependancy on the routers availability trigger. If the router isn't available, all triggers for the switch are suppressed.

[kloczek]

You can use trigger dependencies without templates.

[louis-m]

Hi,
yes I am aware of that. I maybe didn't make myself clear so apologies there.
What I'm trying to say in the above example is:
if a switch that sits behind a router for instance has eg. switch has 100 triggers, rather than create dependancies on all of those triggers, perhaps be able to create a host based dependancy (in this case the switch) that has a master dependancy on the router eg icmp unavailable
So if the router is unreachable, all triggers on the switch are supressed.

Mass update certainly makes it easier (by adding 100 dependancies) but a master dependancy for the host (one dependancy created) would be even easier.

[kloczek]

In other words your RFE is about add in trigger mass update possibility to add triggers dependencies for multiple triggers.
If that is correct just go to https://support.zabbix.com/ and open RFE as ZBXNEXT.