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
Set BAD to WARNING after acknowledgement
Only if you unmark "Treat Warning status as Bad" optionIt looks like when it changes to 'WARNING', the %AckRecurrences% are reset as well
May I ask why do you need to change status?
HostMonitor allows you to set different colors for acknowledged and "fresh" bad tests. View and Report profiles offer filters for acknowledged and "fresh" bad tests, etc.
Regards
Alex
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
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