Trigger related to multiple hosts actions with the undesired result

[bbrendon]

Expression: ({srv2:system.cpu.util[].nodata(755)}=1)&({srv1inger[client.verio].last(0)}=1)
Name: Unresponsive
Host: srv2

This trigger is setup for srv2. If it activates and I get an alert, it says srv1 is down when it should say srv2 is down.

Please fix. Its confusing our engineers!

[Alexei]

This trigger is setup for srv2.

Wrong! The trigger is set for both srv1 and srv2!

[bbrendon]

Thats fine, but how do I get it to say srv1 is down?

This is very annoying. Is there a useful way to use dependencies? This method doesn't help much and using the dependencies in the GUI doesn't work as discussed in a previous thread. Argh.

Help!

[Alexei]

Thats fine, but how do I get it to say srv1 is down?

Trigger name: Both srv1 and srv2 are down.
That is exactly what the trigger suggests!

[bbrendon]

An action fires, and a notification goes out that says srv2 is down. It never says anything about srv1. I realize when you go to the "triggers" menu in the web UI it says both are down, but I really care about srv1, which is the reason for the trigger/action. I'm not getting the important notification.

[Alexei]

An action fires, and a notification goes out that says srv2 is down. It never says anything about srv1.

It is obvioulsy configured to say that "srv2 is down", just configure it differently to have notification of your choice...