It had been long enough that I didn’t recall the exact problem. I checked
the archives. My problem was I was getting multiple recovered
notifications since STOP didn’t include RECOVERED by default. So a
different problem than you are experiencing.
Are you getting all three alerts and recoveries or just the last two
alerts since the DURATION on the first one has not been met?
Here is a note I have in my alerts.cfg on proper use of DURATION and
STOP. Again, may not be your exact problem.
# Here is the proper way to handle a DURATION setting when you don't want
any notification to happen
# until it is in an alert condition for at least 2 minutes.
#
# If you don't use $STOP it will fail to match if the duration is not met.
# It will then NOT stop processing and will fall down to the default alert
notifications which are immediate.
#
# PAGE=%url/.* EXSERVICE=sslcert
# MAIL user-65914449165d@xymon.invalid DURATION>2 REPEAT=60 RECOVERED
# $STOP <-- see definition below
#
*From:* Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid]
*Sent:* Friday, March 1, 2019 1:27 PM
*To:* Larry Bonham
*Cc:* Xymon MailingList
*Subject:* Re: [Xymon] Alerts STOP command not working
I'm getting both red and recovered alerts in my case. In your case were
you not getting red alerts but you were getting recovered messages?
I'm using Xymon 4.3.28 on CentOS 7.6
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
On Fri, Mar 1, 2019 at 2:14 PM Larry Bonham <user-7a867963a09a@xymon.invalid> wrote:
Josh,
This may not be your problem but I had issues in the past similar to
this. My problem turned out to be how RECOVERED was being handled. I’m
using xymon 4.3.28 on Redhat 7.6.
I defined this macro at the top of the rule set in alerts.cfg and replaced
all STOP instances with $STOP.
# !!!!!!!!!! IMPORTANT !!!!!!!!!!!!!!!!!!
# Define macro to halt any further rule evaluation.
# Both IGNORE and RECOVERED are needed.
$STOP=IGNORE RECOVERED
Larry
*From:* Xymon [mailto:xymon-bounces at xymon.com] *On Behalf Of *Josh Luthman
*Sent:* Friday, March 1, 2019 9:11 AM
*To:* Ralph Mitchell
*Cc:* Xymon MailingList
*Subject:* Re: [Xymon] Alerts STOP command not working
Sorry trying to sanitize let me repost...
# tail -n 14 alerts.cfg
HOST=windows10.imaginenetworksllc.com
MAIL user-4c45a83f15cb@xymon.invalid COLOR=RED DURATION>60m REPEAT=60
RECOVERED
STOP
HOST=%.*\.imaginenetworksllc\.com
MAIL user-deaa665bc8d9@xymon.invalid COLOR=RED DURATION>15m RECOVERED
FORMAT=SMS
HOST=*
MAIL user-4c45a83f15cb@xymon.invalid COLOR=RED DURATION>5m REPEAT=60
RECOVERED
# include additional sections
directory /etc/xymon/alerts.d
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
On Fri, Mar 1, 2019 at 10:02 AM Ralph Mitchell <user-00a5e44c48c0@xymon.invalid>
wrote:
Just a minor nit-pick - does the actual file have the same typo in the
hostname in the first entry??
HOST=windows10.imaignenetworksllc.com
Ralph Mitchell
On Fri, Mar 1, 2019 at 9:50 AM Josh Luthman <user-4c45a83f15cb@xymon.invalid>
wrote:
Does anyone have a working example of STOP?
The man page says:
# STOP - Valid for a recipient: If this recipient gets an
# alert, recipients further down in alerts.cfg
# are ignored.
This doesn't seem to be the case, though. The second and third statements
are happening even though the first has a STOP.
HOST=windows10.imaignenetworksllc.com
MAIL user-4c45a83f15cb@xymon.invalid COLOR=RED DURATION>60m REPEAT=60
RECOVERED
STOP
HOST=%.*\.imaginenetworksllc\.com
MAIL user-26969de5aefc@xymon.invalid COLOR=RED DURATION>15m RECOVERED FORMAT=SMS
HOST=*
MAIL user-4c45a83f15cb@xymon.invalid COLOR=RED DURATION>5m REPEAT=60
RECOVERED
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
CONFIDENTIALITY NOTICE:
This electronic mail message is intended exclusively for
recipient to which it is addressed. The contents of this message
and any attachments may contain confidential and privileged
information. Any unauthorized review, use, print, storage, copy,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please advise the sender
immediately by replying to the message's sender and delete all
copies of this message and its attachments without disclosing
the contents to anyone, or using the contents for any purpose.
CONFIDENTIALITY NOTICE:
This electronic mail message is intended exclusively for
recipient to which it is addressed. The contents of this message
and any attachments may contain confidential and privileged
information. Any unauthorized review, use, print, storage, copy,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please advise the sender
immediately by replying to the message's sender and delete all
copies of this message and its attachments without disclosing
the contents to anyone, or using the contents for any purpose.