Dependencies

[bbrendon]

This is regarding 1.1.2, after this problem I upgraded to 1.1.4, but I'm not sure if it works yet.

I have a test running to see if a gateway is down. If its down, the trigger activates and stays active for at least 5 minutes.

If the gateway trigger is active, I don't want to know if the host is down. I therefore have a nodata() trigger depend on the above gateway trigger.

This scenario did not work with 1.1.2 and I'm assuming it won't in 1.1.4 because the changelog doesn't say this was fixed.

Even if its an inverse dependency configuration error, I get trigger activations for the host being down even when the gateway trigger is on or off. This tells me that the dependency has no effect.

Bug? Feature? User error?

[bbrendon]

Confirmed as not working in 1.1.4

[Alexei]

You still get trigger activation by no actions will be executed for this trigger.

[bbrendon]

Is that a question or statement? Either way, I don't quite understand.

[Alexei]

Sorry, I din't check my message before posting, typing too fast...

Currently trigger dependencies affect execution of actions only. It means that these triggers will normally change their statuses, however they will not appear in Status of Triggers screen and won't generate actions.