Alex,
If I set a test to (In this example a service test)
Treat Unknown : Not checked
Treat Warning status as Bad: Checked
Use Warning status if Checked: Checked -- set to: ('%SimpleStatus% '=='DOWN)'
Use Normal Status: Not Checked
When the test status is DOWN the status is correctly set to warning, when the status is UP the test remains in the warning state. I think it should go back to normal.
The reason we have made this test is that we want to trigger an action when the service is not running, but we do not really consider this a Failure, so we we do not want to display "BAD" only warning.
Issue with Treat Warning Status as Bad
Correct behavior, you are using wrong variable.
Quote from the manual
Alex
Quote from the manual
RegardsIMPORTANT note: HostMonitor checks logical expressions after test check is done and "reverse alert" option is processed.
I.e.
- HostMonitor performs the test;
- processes "Reverse alert" option;
- sets "suggested" macro variables (%SuggestedStatus%, %SuggestedSimpleStatus%, %SuggestedReply%, %SuggestedRecurrences% and %FailureIteration%) without touching regular counters (%Status%, %Reply%, %Recurrences%, etc);
- then HostMonitor checks "Warning" and "Normal" expressions, processes "Tune up Reply" option and finally modifies current test status and statistisc counters (Status, Reply, Alive%, Passed tests, Failed tests, etc).
Alex