[Bigsister-general] "General to specific" alarming rules not working?

["Christopher Hatty" <suppressed>]

I guess I should join the list BEFORE submitting the question!

My understanding of how alarming works is that if multiple definitions
match an event then the last one in the file is the one that is applied.

Take, for example, a snippet of my bb_event_generator.cfg file:

*.*     prio=20 down=yellow up=green delay=5 \
        check="$host.conn and ((not '$router') or $router.conn)" \
        norepeat=20 keep=1 suppressed repeatprio=10
msgmax=60 \
        maxpermin=20

*.cpu   prio=40 down=red up=green delay=5 \
        check="$host.conn and ((not '$router') or $router.conn)" \
        norepeat=20 keep=1 suppressed repeatprio=20
msgmax=20 \
        maxpermin=5

specific_host.*	down=red suppressed

specific_host.cpu	down=purple suppressed

What we're saying here is that
1) IN GENERAL, we want status "yellow" events to send mail to a specific
address
2) if the event is CPU, then we want mail sent only when status = red,
but to a different address (my pager, in fact)
3) for specific hosts, we want mail send only when the status is red
4) for specific hosts, if the event is a CPU alert, we only want mail
sent if the status is purple

Does this look right?

What is actually happening is that for general hosts, things are working
as expected, but specific hosts are sending mail when CPU is red rather
than purple. It looks like the re-definition of "down" is being ignored.

Can anyone help shed some light on this or tell me what I am doing
wrong?

Thanks
Christopher

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bigsister-general mailing list
suppressed
https://lists.sourceforge.net/lists/listinfo/bigsister-general