Cross-Template Dependencies

[Crazy Marty]

For my "application group" templates, I need to have most of the triggers depend on triggers from other templates. For instance, it doesn't make sense to have a MySQL trigger (from template T_MySQL) if the host is unreachable (from template T_Linux). I *really* don't want to duplicate all the dependencies in each application group! That way lies madness!

[Crazy Marty]

I just realized it is much worse than this! I have several Physical machines hosting several Virtual machines each. If the Physical host (Template_Linux) is unreachable, I do not want alerts going off about the Virtual hosts (Template_Linux, Template_Windows, Template_SNMPv1Device, etc.) running there!

[Alexei]

If the Physical host (Template_Linux) is unreachable, I do not want alerts going off about the Virtual hosts (Template_Linux, Template_Windows, Template_SNMPv1Device, etc.) running there!

Configure trigger dependencies and you will be all right...

[Crazy Marty]

Hmmm. My bad, it seems. I guess I didn't think to use the dropdown to select the right template when setting that up. That has messed with my head in the past as well.

But, relatedly, shouldn't (some, many, most, all) of the triggers in Template_Linux have a dependency on Template_Linux:unreachable by default?

[Alexei]

But, relatedly, shouldn't (some, many, most, all) of the triggers in Template_Linux have a dependency on Template_Linux:unreachable by default?

Even triggers related to CPU usage? Why?

One availability trigger may depend on another availability trigger; it makes no sense to make ALL triggers dependable on host availability.