Xymon Mailing List Archive search

hobbit alert and STOP messages

3 messages in this thread

list Christopher T. Beers · Sat, 09 Apr 2005 22:43:21 -0400 ·
I am having some difficulties with the STOP rules when an alert is triggered.  I have the following rule in my hobbit-alert file.

HOST=somehost.syr.edu
        MAIL user-96213c045646@xymon.invalid REPEAT=30m RECOVERED STOP
        MAIL user-6bd70174da6f@xymon.invalid REPEAT=15m FORMAT=SMS RECOVERED STOP

My understanding is that the alert module should alert me and the pager when the alert triggers.  However, it appears that when the alert module encounters the STOP keyword it stop processing the entire rule (instead of stopping only if the recipient has already been alerted).

Is this intended and if so how do I accomplish alerting two users for alert rules?

Note:  I was running beta6 when this problem occurred.  I have updated to 4.0.1 with the eventlog patch, so maybe its fixed there.

-- 
Christopher T. Beers
Lead UNIX Architect - System Infrastructure Services (SIS)
Syracuse University | 250 Machinery Hall | Syracuse, NY XXXXX
(XXX) XXX-XXXX Office | (XXX) XXX-XXXX Fax | user-62463a5fbf92@xymon.invalid Pager
list Henrik Størner · Sun, 10 Apr 2005 08:59:20 +0200 ·
quoted from Christopher T. Beers
On Sat, Apr 09, 2005 at 10:43:21PM -0400, Christopher T. Beers wrote:
I am having some difficulties with the STOP rules when an alert is triggered.  I have the following rule in my hobbit-alert file.

HOST=somehost.syr.edu
       MAIL user-96213c045646@xymon.invalid REPEAT=30m RECOVERED STOP
       MAIL user-6bd70174da6f@xymon.invalid REPEAT=15m FORMAT=SMS RECOVERED STOP

My understanding is that the alert module should alert me and the pager when the alert triggers.  However, it appears that when the alert module encounters the STOP keyword it stop processing the entire rule (instead of stopping only if the recipient has already been alerted).

Is this intended and if so how do I accomplish alerting two users for alert rules?
This is the intended behaviour - the "STOP" keyword is definitive.
I believe you should just remove the STOP keyword from the first
recipient line.


Regards,
Henrik
list Christopher T. Beers · Sun, 10 Apr 2005 12:20:36 -0400 ·
You are right - as usual and I figured that out last night right after I 
sent it.

Thanks for your help.
signature

-- 
Christopher T. Beers
Lead UNIX Architect - System Infrastructure Services (SIS)
Syracuse University | 250 Machinery Hall | Syracuse, NY XXXXX
(XXX) XXX-XXXX Office | (XXX) XXX-XXXX Fax | user-62463a5fbf92@xymon.invalid Pager

quoted from Henrik Størner
--On April 10, 2005 8:59:20 AM +0200 Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:

| This is the intended behaviour - the "STOP" keyword is definitive.
| I believe you should just remove the STOP keyword from the first
| recipient line.