Hey Alex,
For some tests that turn OK automatically when UP again after a DOWN status (like Ping, CPU usage etc.) I want to keep the "BAD" status after an alarm.
The ideal situation for me would be like this:
- BAD status: System is down (for example Ping)
- WARNING status: System is up again but it isn't acknowledged
- OK status: System is up and acknowledged
Is there any way to accomplish this?
Thank you
Keep bad status until acknowledged
Forgot to say:
Right now I can create the WARNING status when the system is up again but not acknowledged.
To do this I use the 'Use warning if' function:
('%SuggestedStatus%'=='Host is alive' and %CurrentStatusDuration_sec%<120) or (%StatusID%==14 and %AckRecurrences%==0)
The CurrentStatusDuration is used to check only 'new' alive hosts (within 120 seconds), if this macro isn't used all 'alive hosts' will turn to warning status.
The second part of the row is to keep the Warning status when not acknowledged.
And 'use normal status if'
('%SuggestedStatus%'=='Host is alive' and %AckRecurrences%==1) or (%StatusID%==14 and %AckRecurrences%==1)
This row is actually the same but it checks if the tests is acknowledged.
The problem is:
For some reason the Macro %AckRecurrences% stays 0 even when I have acknowledged the Warning status!
Now my test stays on 'Warning' all the time instead of switching to 'Normal' after acknowledgement
Right now I can create the WARNING status when the system is up again but not acknowledged.
To do this I use the 'Use warning if' function:
('%SuggestedStatus%'=='Host is alive' and %CurrentStatusDuration_sec%<120) or (%StatusID%==14 and %AckRecurrences%==0)
The CurrentStatusDuration is used to check only 'new' alive hosts (within 120 seconds), if this macro isn't used all 'alive hosts' will turn to warning status.
The second part of the row is to keep the Warning status when not acknowledged.
And 'use normal status if'
('%SuggestedStatus%'=='Host is alive' and %AckRecurrences%==1) or (%StatusID%==14 and %AckRecurrences%==1)
This row is actually the same but it checks if the tests is acknowledged.
The problem is:
For some reason the Macro %AckRecurrences% stays 0 even when I have acknowledged the Warning status!
Now my test stays on 'Warning' all the time instead of switching to 'Normal' after acknowledgement
%AckRecurrences% == 0 because HostMonitor clears acknowledgment flags when test status changes back to "good" ('Host is alive" or "Normal").For some reason the Macro %AckRecurrences% stays 0 even when I have acknowledged the Warning status!
We checked several options but did not find nice solution that can help you but will not change existing behavior for other customers, yet.
Actually we made small modification but it will not help you in this case.
Probably we can add several new variables...
Regards
Alex
Yes you're right!KS-Soft wrote: %AckRecurrences% == 0 because HostMonitor clears acknowledgment flags when test status changes back to "good" ('Host is alive" or "Normal").
I decided to do it another way...
Right now I change the test interval when a bad result occurs (using actions). The alarm stays on the screen because the test interval changed to a couple of hours. After that I acknowledge AND refresh the test.
The test refreshes because I set up a 'restore test interval' action when %AckRecurrences% == 1.
When I acknowledge AND refresh the test, it turns acknowledged (yellow row on my screen) if not up and it turns OK if up again. I decided to do nothing with the 'warning' status.
Most important is that alarms that occur at night are seen by our employees and that they can see when a test is acknowledged.
Maybe you could add a funtion for these tests like: 'if "Bad" status > Do not test until Acknowledged'?
Anyway, thanks for your help Alex!
