Set BAD to WARNING after acknowledgement

[Kris]

Hi guys,

I was wondering if it was possible to set a BAD back to WARNING after is is acknowledged.
Been tinkering with the 'Use Warning Status' setting, but I can't get it right.

Ideas?

Thanks,
Kris

[KS-Soft]

Use Warning status if ('%SimpleStatus%'=='DOWN') and (%AckRecurrences%>0)

Regards
Alex

[Kris]

Hi Alex,

That is what I tried, but it will make it flip-flop between WARNING and BAD

[KS-Soft]

My mistake

Use Warning status if ('%SuggestedSimpleStatus%'=='DOWN') and (%AckRecurrences%>0)

Regards
Alex

[Kris]

Hi Alex,

Unfortunately, that doesn't work either.
It looks like when it changes to 'WARNING', the %AckRecurrences% are reset as well, making it 'BAD' again... and so on

[KS-Soft]

[Kris]

Hi Alex,

This is the case:
We use TeamViewer to give external consultants access to our servers.
This is on a per-request basis.
We have a test on each server that monitors the presence of the TeamViewer process.
Once it is detected, we acknowledge it with the reason.
Then, it is no longer 'BAD', because we know why it is running.
But it still should have the 'WARNING' status, because we need to keep an eye on it and make sure TeamViewer is shut down once the consultant is done.

So, no big deal. Just trying to tweak it

[KS-Soft]

You may use different color for Bad acknowledged test and/or keep default "Treat Warning status as Bad" option so HostMonitor will not reset Ack flag and you will get Warning status.

Regards
Alex