Trigger Dependencies - How do I set it up quickly?

[andreas777]

Hello!

I want to make trigger dependencies on template basis or something like that.

My scenario in short:

I have about 35 remote locations (monitored directly from the zabbix server via VPN).
Each has a Modem, Router, and then about 5-10 devices directly connected to the router.
The modem is the most central point in terms of Internet Access. If this device fails all devices will be unavailable. The router is the next central point and the clients are all connected directly to the router.

So my Trigger Dependency would look like this:

Location 1:

		Modem
		Router
Device1	Device2	Device3	Device4	Device5

Now, I would have to set each trigger on each device to be dependent from the router and the router itself from the modem.
And this I would have to repeat 35 times for each remote location. And if devices are added in the future, I'd have to make them manually dependent again.

Isn't there a faster way? I can't believe that guys with about 1000+ devices do this all by hand.

Thanks in advance

Andreas

[Markku]

Those who have thousands of devices most often do the configurations using Zabbix API.

Markku

[andreas777]

Ok, but isn't there a faster way without using the API?

[Markku]

Ok, but isn't there a faster way without using the API?

I don't know your definition of "fast" in this context, but in the GUI you can filter the trigger list so that you can mass update the dependencies on all triggers on all filtered hosts (for example for one location) at the same time.

[andreas777]

Your suggestion was fast enough for me. Thank you!
The Trigger-List is just a bit hidden. 'Cause I never really realized before that you could extend the trigger list at the place where you are displaying the triggers from a host.

[Markku]

Those who have thousands of devices most often do the configurations using Zabbix API.

Markku

[andreas777]

Ok, but isn't there a faster way without using the API?

[Markku]

Ok, but isn't there a faster way without using the API?

I don't know your definition of "fast" in this context, but in the GUI you can filter the trigger list so that you can mass update the dependencies on all triggers on all filtered hosts (for example for one location) at the same time.

[andreas777]

Your suggestion was fast enough for me. Thank you!
The Trigger-List is just a bit hidden. 'Cause I never really realized before that you could extend the trigger list at the place where you are displaying the triggers from a host.