Warning counts as dead time

[Mellertm]

I have configured several tests to use optional status processing, the check box 'treat warning status as bad' is unchecked, 'use warning status if' (for example) from a ping test contains:

'%Reply%'>"200 ms"

This will trigger a warning when the response time is higher then 200ms.

Although the test is not 'bad' when the warning is triggered (the host is not down, it just triggered a warning condition), tests resulting in a warning status will count as dead time.

The same counts for unc space checks, i have configured them to go 'bad' at less then 5% free space, but a warning will be given when free space is between 5% and 10% (expression: '%Reply%'>"5 %" and '%Reply%'<"10 %"). Here the warning also counts as dead.

Also, when a test goes into warning, and the next status is Ok, hostmonitor will send a good action email. Although the test was never really bad (it was, but i told HM to use warning).

In the help files i saw that this behavior is by design, can i change this behavior?

[KS-Soft Europe]

I have configured several tests to use optional status processing, the check box 'treat warning status as bad' is unchecked, 'use warning status if' (for example) from a ping test contains:

'%Reply%'>"200 ms"

This will trigger a warning when the response time is higher then 200ms.

I would recommend to use expression like
%SuggestedReply_Integer%>200
instead of
'%Reply%'>"200 ms"

Although the test is not 'bad' when the warning is triggered (the host is not down, it just triggered a warning condition), tests resulting in a warning status will count as dead time.

The same counts for unc space checks, i have configured them to go 'bad' at less then 5% free space, but a warning will be given when free space is between 5% and 10% (expression: '%Reply%'>"5 %" and '%Reply%'<"10 %"). Here the warning also counts as dead.

Quote from manual:
http://www.ks-soft.net/hostmon.eng/mfra ... baddetails
=========================
Warning status always increments "bad" counters (Dead time, Failed tests, Dead ratio, etc)
=========================

Also, when a test goes into warning, and the next status is Ok, hostmonitor will send a good action email. Although the test was never really bad (it was, but i told HM to use warning).

In the help files i saw that this behavior is by design, can i change this behavior?

You may use "Action depends on bad one" option for "Good" actions.

Quote from the manual
=========================
Action depends on "bad" one
This optional parameter is available for "Good" actions only. You can set "Good" action dependable on a "Bad" action. Why do you need it? For example you defined "Bad" action to send an e-mail notification to the network administrator when test fails 3 times consecutively (start when 3 consecutive "Bad" results occur), also you defined «Good» action to send a notification when the test status changes to "Good". What will happen if test fails 1 or 2 times and after this it restores "Good" status? HostMonitor will not send a notification about failure (because test did not fail 3 times) but the program will send notification about restoring "Good" status. To avoid unnecessary "Good" action execution you can mark "Action depends on "bad" one" option and select "Bad" action. In this case HostMonitor will start "Good" action only if corresponding "Bad" action was executed.

=========================

[KS-Soft]

PS
If you do not want to start "bad" actions on this status and you do not want to calculate "bad" statistics, then you don't need Warning status. You should use Normal status instead.
I assume you just want to display such test items using different color?

Regards
Alex

[Mellertm]

I would recommend to use expression like
%SuggestedReply_Integer%>200
instead of
'%Reply%'>"200 ms"

Thanks!

You may use "Action depends on bad one" option for "Good" actions.

Exactly what i needed!

PS
If you do not want to start "bad" actions on this status and you do not want to calculate "bad" statistics, then you don't need Warning status. You should use Normal status instead.
I assume you just want to display such test items using different color?

Sort of, i use the warning status for grace periods for example with CPU usage, polls every 10 minutes, gives warning first 2 times, then the test will go to bad. Effectively: when a process is using more then 80% of cpu, i may run for a maximum of 30 minutes, after that the process should be finished, or hostmonitor will generate an alert.

The same applies for disk space, i use the warning status for non-critical conditions, wich can change in critical conditions over time.

Thanks for your answers!