Trigger dependency, 70% alert and then 90% alert

[muelli]

Hello Forum,

I have a small problem with dependent triggers (I think).
At the moment I have 2 triggers, each fires for the same item at different usage levels. One fires if a level is at >70% for 15m, one if it is at >90% for 15m.

The triggers are built to fire like this:

trigger 1:
min(/TestTemplate/test.value,15m)>70

trigger 2:
min(/TestTemplate/test.value,15m)>90

I was thinking, that if the 70% trigger depends on the 90% trigger, this will happen:
- level reaches 70% -> trigger 1 fires
- level reaches 90% -> trigger 2 fires AND trigger 1 is switching off

Am I correct or have I understood this wrong? I am not sure on how to interpret that recursive hint on the documentation page....

Or is there a better way on doing this?

Thanks!

[cyber]

Well, trigger dependencies are a bit tricky...They are really meant for dependencies between triggers about different things... Thus those examples of hosts and routers dependencies in docs...

In your case, both triggers are about same item.... if you make first one depending on second one, then at the moment second one fires, first one is hidden from the recent problems list, but it is not closed. you can still see it, if you select "history" under problem list... Right when second trigger is not valid any more, first one pops up in recent problems list (again). And disappears from there only if it is no more valid.

you can easily test it with simple trapper item and 2 triggers, "item value> 70" and "item value > 90", first one must be dependent on second one. Send values 75, 95, 85 and 65 and after each observe trigger behaviour.

If you want first one to close, when other is fired, then you do not need dependency, but second part of expression ".. and min(/TestTemplate/test.value,15m)<=90". In that case this trigger becomes not valid when second triggers expression is valid.

[muelli]

Thanks!
This one I already did:
"AND min(/TestTemplate/test.value,15m)<=90"

BUT... then the user complained, that this trigger with logical AND connected condition does not show up in the graph which plots this value thus my idea with the dependency....
Could it also be done via the CLOSE condition? If I use a close condition like "min(/TestTemplate/test.value,15m)>90" then this would close the 70% trigger I think....

[cyber]

You mean with recovery expression...? No. Recovery expression is additional condition, which is considered, when trigger expression is already turned false. For example, if you have a trigger limit at 70 and you want trigger to disappear only after value is below 50.... Then recovery expression keeps it active until value drops below 50.
Basically, if your original condition is min>70 then in case of min>90 it is still true.. So that kind of recovery expression would be nonsense.

[muelli]

OK, I see... Well then I will keep it this way, thanks for your feedback