We have the problem, that in one of our monitored hosts an assigned template doesn't get "resolved" correctly, exactly the defined trigger-dependencies are incorrect.
in the last screenshot you can see the incorrect resolution for the dependency of the trigger: "vacsvr11.veda.de: Laufwerk c: (>80%)"
the dependency of the trigger "vacsvr11.veda.de: Laufwerk d: (>80%)" got resolved correctly, when we changed the trigger definition in the template after we assigned the template to the host "vacsvr11"
we would be happy, if anyone could shed some light on this.
kind regards
Michael
Here some screenshotsof our trigger-definitions:
(the triggers are defined like: "{HOSTNAME}: Laufwerk c: (>90%)")
template definition:

correct host-triggers:

incorrect host-triggers:
in the last screenshot you can see the incorrect resolution for the dependency of the trigger: "vacsvr11.veda.de: Laufwerk c: (>80%)"
the dependency of the trigger "vacsvr11.veda.de: Laufwerk d: (>80%)" got resolved correctly, when we changed the trigger definition in the template after we assigned the template to the host "vacsvr11"
we would be happy, if anyone could shed some light on this.
kind regards
Michael
Here some screenshotsof our trigger-definitions:
(the triggers are defined like: "{HOSTNAME}: Laufwerk c: (>90%)")
template definition:
correct host-triggers:
incorrect host-triggers:
Comment