Hi everyone,
After doing some testing I can say we've elegantly solved the problem
caused by "HOST=%^asd$" matching both hosts named "asd" and "asdf" despite
the "$" at the end. We've added a "STOP" rule at the end of the "special"
rules that only alert CTO & CEO of Junkyard.
The problem still remains, however.
The new, most elegant ruleset thus far, follows:
--- cut here ---
HOST=junkyard-starbox-v_trash
MAIL=user-931218b43962@xymon.invalid
STOP
HOST=junkyard-starbox-x_dustbin
MAIL=user-239f7abe1b7a@xymon.invalid
STOP
HOST=*
MAIL=user-c3a820d2604a@xymon.invalid REPEAT=60 RECOVERED NOTICE COLOR=purple,yellow
MAIL=user-c3a820d2604a@xymon.invalid REPEAT=10 RECOVERED NOTICE COLOR=red
MAIL=user-6d9e746345af@xymon.invalid DURATION>60 REPEAT=60 RECOVERED NOTICE
COLOR=purple,yellow
MAIL=user-6d9e746345af@xymon.invalid DURATION>30 REPEAT=60 RECOVERED NOTICE COLOR=red
--- and here ---
On Thu, Jan 28, 2010 at 10:45 PM, Kii NODA <user-d20081af5452@xymon.invalid> wrote:
Hi everyone,
As you may have already been aware by now, we're here to stay. :)
Here's one interesting problem (and maybe simple) for you: We've seen that
"HOST=%^asd$" matches both hosts named "asd" and "asdf", not respecting the
"$" at the end. Can you guys please confirm that regex matching for "HOST="
does not care about the "$" sign?
For those that need some expanded case-study (all others can now stop),
here's the story behind: we are managing various servers of ours and our
customers. Due to the fact that we do not control DNS entries for all these
machines we have come up with a naming scheme like this:
--- cut here ---
junkyard-starbox # clientID=junkyard, starbox=actual machine
junkyard-starbox-v_trash # v_trash=vserver named trash running on starbox
junkyard-starbox-v_trashcan # v_trashcan=vserver named trashcan running on
starbox
junkyard-starbox-x_dustbin # x_dustbin=xen server running on starbox
--- and here ---
We need to send these "special" alerts:
* ONLY user-931218b43962@xymon.invalid for events on junkyard-starbox-v_trash
* ONLY user-239f7abe1b7a@xymon.invalid for events on junkyard-starbox-x_dustbin
Also, we need to send these alerts for all other hosts & events:
* user-c3a820d2604a@xymon.invalid for purple, yellow & red w/ REPEAT=60
* user-6d9e746345af@xymon.invalid for red w/ DURATION>30 and REPEAT=60
* user-6d9e746345af@xymon.invalid for yellow&purple w/ DURATION>60 and REPEAT=60
Exercising our brain muscles we came up with these:
--- cut here ---
#alert CTO for v_trash
HOST=junkyard-starbox-v_trash
MAIL=user-931218b43962@xymon.invalid
#alert CEO for x_dustbin
HOST=junkyard-starbox-x_dustbin
MAIL=user-239f7abe1b7a@xymon.invalid
#stop alerting for the private boxes above
HOST=*
IGNORE HOST=%^junkyard-starbox-(v_trash|x_dustbin)$
HOST=* COLOR=purple,yellow
MAIL=user-c3a820d2604a@xymon.invalid REPEAT=60 RECOVERED NOTICE
MAIL=user-6d9e746345af@xymon.invalid DURATION>60 REPEAT=60 RECOVERED NOTICE
HOST=* COLOR=red
MAIL=user-c3a820d2604a@xymon.invalid REPEAT=10 RECOVERED NOTICE
MAIL=user-6d9e746345af@xymon.invalid DURATION>30 REPEAT=60 RECOVERED NOTICE
--- and here ---
However, even with the "$" at the end of our regex we are no longer
receiving any alerts for v_trashcan because the regex wrongly matches on the
"IGNORE HOST=" line. We could use 2 lines to match each host on its own line
but that's not the point of this exercise.
So, can anyone confirm our finding?