-
Type:
New Feature Request
-
Resolution: Fixed
-
Priority:
Critical
-
Affects Version/s: None
-
Component/s: API (A), Frontend (F), Server (S)
Many users find use of trigger hysteresis quite difficult due to inverse logic when using {TRIGGER.VALUE} in expressions. Probably the best approach is to support two trigger expressions: one to go into problem state, another - for recovery (OK). The second trigger expression should be optional.