Hi,
I noticed the following case where the PROBLEM -> OK trigger state design does not quite correspond with the real usage.
If we have an equipment/app to monitor and the equipment is restarting I don't think in all cases the trigger should have 2 states: PROBLEM (when detecting restart) and then OK (when device has recovered). I think a restart is just one time state event.
What bugs me is I am getting 2 events for such situation... There is any way to have only one event (just the PROBLEM) about such situations?
Probably customizing actions would lead to removing the OK notification but still, the OK even will exists into the system and will be reported under backend.
I noticed the following case where the PROBLEM -> OK trigger state design does not quite correspond with the real usage.
If we have an equipment/app to monitor and the equipment is restarting I don't think in all cases the trigger should have 2 states: PROBLEM (when detecting restart) and then OK (when device has recovered). I think a restart is just one time state event.
What bugs me is I am getting 2 events for such situation... There is any way to have only one event (just the PROBLEM) about such situations?
Probably customizing actions would lead to removing the OK notification but still, the OK even will exists into the system and will be reported under backend.
Comment