Hi.
I'm testing CPU load on a server every 2 minutes and set alert when CPU usage more than 95%. In action profile i set sending e-mail after 4 consecutive "Bad" results occur and sending e-mail after 1 "Good" results occur. So if CPU load on a server more than 95% for a 8 minutes long i recieve e-mail message of bad status and after CPU load is in a good state i recieve e-mail that it's ok. But i recieve e-mail message that CPU is good without recieving message that it's bad when one of four consecutive test was "Bad". Can HostMonitor set "Bad" status after a few checks with bad statuses?
I would like to do this for ping test too. For example i'm testing remote host with a ping test. If the first check is "no reply" then this test set in "warning" state. If the next check is "no reply" then this test set in "Bad" state with some actions (e-mail, sound alarm, etc). When test is in a "good" state it's checks every few seconds or minutes (i can set it in "Test every" field). But when test in "warning" state next check will be after other time.
Thank you.
Set bad status after few tests.
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Re: Set bad status after few tests.
I think you may use "Action depends on "bad" one" option.
Qoute from manual:
==================
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.
==================
http://www.ks-soft.net/hostmon.eng/mfra ... properties
Regards,
Max
Qoute from manual:
==================
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.
==================
http://www.ks-soft.net/hostmon.eng/mfra ... properties
Regards,
Max