Xymon Mailing List Archive search

info page and alerts

2 messages in this thread

list Christopher T. Beers · Sat, 26 Mar 2005 11:24:34 -0500 · 
Seems like the info page does not understand the STOP and UNMATCHED keywords.  I have a server that I set alarms based on hostname to 2 particular addresses with the STOP keyword.  At the bottom I have a catchall UNMATCHED rule.

The info page on hobbit shows the alerts for both the STOP and UNMATCHED set, but hobbit only alarms the STOP rules.  Maybe a bug?

-- 
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 · Sat, 26 Mar 2005 17:02:36 +0000 (UTC) ·
▸ quoted from Christopher T. Beers
In <user-0a99f90faef6@xymon.invalid> "Christopher T. Beers" <user-96213c045646@xymon.invalid> writes:

Seems like the info page does not understand the STOP and UNMATCHED keywords.  I have a server that I set alarms based on hostname to 2 particular addresses with the STOP keyword.  At the bottom I have a catchall UNMATCHED rule.
The info page on hobbit shows the alerts for both the STOP and UNMATCHED set, but hobbit only alarms the STOP rules.  Maybe a bug?
It shows both the STOP and UNMATCHED rules, because when generating
the info-page it is not possible to determine if the STOP or UNMATCHED
will trigger - that might depend on circumstances such as the
time-of-day when the alert happens.

There is a code to tell you that it's a stop-rule: It has "(S)" after
the recipient. UNMATCHED isn't flagged like that, which is a bug.


Regards,
Henrik