Perform action when operator ACKs an alerting test
Perform action when operator ACKs an alerting test
We're on HM 8.82, and we'd like HM to send an email when an operator ACKs an alerting test. That way, when one operator stops the alerts, other operators will know why the alerts stopped. If this is already a feature, I must be missing it.
You may use advanced mode action and %AckRecurrences% or %AcknowledgedBy% variables.
Quote from the manual
=====================
%AckRecurrences%
Represents the number of test probes which have returned similar (bad or unknown) result after it was already acknowledged. Returns 0 for non-acknowledged test items.
For example if the test returned "bad" status during five consecutive probes, then %Recurrences% variable will be equal 5. If the user has acknowledged the bad status after the second probe then %AckRecurrences% will be equal 3 (5-2=3).
This variable is useful when you want to configure alert profile to launch different actions for "non-acknowledged" and "acknowledged" test items. E.g. if condition to trigger action execution looks like ('%SimpleStatus%=='DOWN') and (%AckRecurrences%==1), HostMonitor will start action when user confirmed status and test failed once again (after acknowledgement).
=====================
Advanced actions: http://www.ks-soft.net/hostmon.eng/mfra ... ncedaction
Macro variables: http://www.ks-soft.net/hostmon.eng/mfra ... .htm#macro
Regards
Alex
Quote from the manual
=====================
%AckRecurrences%
Represents the number of test probes which have returned similar (bad or unknown) result after it was already acknowledged. Returns 0 for non-acknowledged test items.
For example if the test returned "bad" status during five consecutive probes, then %Recurrences% variable will be equal 5. If the user has acknowledged the bad status after the second probe then %AckRecurrences% will be equal 3 (5-2=3).
This variable is useful when you want to configure alert profile to launch different actions for "non-acknowledged" and "acknowledged" test items. E.g. if condition to trigger action execution looks like ('%SimpleStatus%=='DOWN') and (%AckRecurrences%==1), HostMonitor will start action when user confirmed status and test failed once again (after acknowledgement).
=====================
Advanced actions: http://www.ks-soft.net/hostmon.eng/mfra ... ncedaction
Macro variables: http://www.ks-soft.net/hostmon.eng/mfra ... .htm#macro
Regards
Alex
I believe I have it set up, using:
As the condition.
However, when an operator does ACK/Stop (because we have email-to-SMS configured to repeat with -1), the actions are stopped, and this action - sending an email when the alert has been ACKed - never triggers. So we don't get an email when someone does ACK/Stop.
I hope that makes sense.
Code: Select all
('%SimpleStatus%=='DOWN') and (%AckRecurrences%==1)
However, when an operator does ACK/Stop (because we have email-to-SMS configured to repeat with -1), the actions are stopped, and this action - sending an email when the alert has been ACKed - never triggers. So we don't get an email when someone does ACK/Stop.
I hope that makes sense.
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
That still doesn't work, and for the reasons I was thinking: when an operator does ACK/Stop, the step in the action profile that applies *after* the ACK/Stop never runs, because alerts are *stopped.*
So, instead, I've changed my email-to-SMS step in the action profiles to look something like this:
So, when the status is DOWN, and after two iterations of it being down, and *only if* the test is not ACKed, this step will generate an action (email to a group containing SMS contacts).
Now, I will instruct my operators to use ACK instead of ACK/Stop; ACK will stop the repeating email from this step, and still allow the other step, where an email is sent giving the ACK details.
So, instead, I've changed my email-to-SMS step in the action profiles to look something like this:
Code: Select all
('%SimpleStatus%'=='DOWN') and (%CurrentStatusIteration%>=2) and (%AckRecurrences%==0)
Now, I will instruct my operators to use ACK instead of ACK/Stop; ACK will stop the repeating email from this step, and still allow the other step, where an email is sent giving the ACK details.