notify up only after previous notify down

All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
Post Reply
StrongForce
Posts: 2
Joined: Thu Oct 07, 2004 9:52 pm

notify up only after previous notify down

Post by StrongForce »

We are doing some checks, could be ping, could be http content. We want to allow (in some cases) 3 or more failures before it would email an alert or notification. We can do that fine, however when it then succeeds we get notified the system is up. We don't want those up notifications unless it has failed 3 time and notified us down 1st. See, we are getting up pages with out a previous down page at this point.... the way we have it set.
thanks.
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

Its easy - use "Action depends on bad one" option (mark this option for your "good" action").
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
StrongForce
Posts: 2
Joined: Thu Oct 07, 2004 9:52 pm

Post by StrongForce »

Thanks. Right under our nose. That's the ticket. We were making things too hard on ourselves with macros and master, slave stuff.
Post Reply