Henrik,
So what you're saying is that when you have a TIME blackout window for a
service, even if the last rule for that service has STOP after it, the
alerts continue until it finds a rule it can send with?
That if it is what you are saying is not something I would be expecting.
Just so you can see, these are the two lines 137 and 139.
MAIL=user-d5da4a3e59bc@xymon.invalid COLOR=red,yellow REPEAT=1h FORMAT=PLAIN
MAIL=user-fca9e44cc8cf@xymon.invalid COLOR=RED FORMAT=SMS
DURATION>5 REPEAT=1h
Regards,
Mike
-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: 19 June 2006 11:43
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] TIME alert problems (still)
On Mon, Jun 19, 2006 at 10:38:17AM +0100, Mike Rowell wrote:
Henrik,
On 137 and 139 we have the catch alls for sysalert and support
(support
is our red address and sysalert is where we send both to).
Well, those catch-all rules are what triggers the alerts you don't want.
They probably have a "UNMATCHED" setting ? But that will also cause
them to be applied when the rules above them are skipped due to time-
constraints.
In other words, if you have a setup like
HOST=myhost TEST=mytest
MAIL user-c0b4a5e3f417@xymon.invalid TIME=W:0800:1700
HOST=*
MAIL user-9a4e95710e98@xymon.invalid UNMATCHED
then "user-9a4e95710e98@xymon.invalid" will get all myhost.mytest alerts
that happen outside the weekdays-0800-1700 time window.
Regards,
Henrik
This email has been scanned for all viruses by the MessageLabs service.
This email has been scanned for all viruses by the MessageLabs service.