I have some tests configured to only send an email if they are bad twice in a row (for example). But I cannot work out how to stop the email being sent to say that the test is OK again in the situation where it is only bad the once.
This creates extra emails that cause confusion because then you go and check to find the Alert (Bad) email but it doesn't exist, etc.
How do I tell the test to only send the OK email if the test was bad 2 or more times in a row before going OK again.
I am guessing there might be a way with the Advanced mode but I get a bit confused writing these scripts so any help on that appreciated.
Preventing unnecessary OK emails
Re: Preventing unnecessary OK emails
You only need to active "Action depends on "bad" one" in the action properties page from the "good" actionmeppyman wrote:I have some tests configured to only send an email if they are bad twice in a row (for example). But I cannot work out how to stop the email being sent to say that the test is OK again in the situation where it is only bad the once.
This creates extra emails that cause confusion because then you go and check to find the Alert (Bad) email but it doesn't exist, etc.
How do I tell the test to only send the OK email if the test was bad 2 or more times in a row before going OK again.
I am guessing there might be a way with the Advanced mode but I get a bit confused writing these scripts so any help on that appreciated.
Regards,
MP
Correct.
There is 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.
==========================
Regards
Alex
There is 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.
==========================
Regards
Alex
Yep it was one of those things that was staring me in the face and I didn't see it.
You know I might just have to write up my own guide to setting up HostMonitor based on experience and written in a way that is practical and gives good examples of all the options... will be useful but a bit of an undertaking.
You know I might just have to write up my own guide to setting up HostMonitor based on experience and written in a way that is practical and gives good examples of all the options... will be useful but a bit of an undertaking.