Combination of keywords in rules
list Etienne Roulland
Hi, i'm trying to set rules with multiples conditions like "COLOR=red "and" SERVICE=* "and" DURATION>6m REPEAT=15m RECOVER" But i don't find how . Events are matching if COLOR is RED "OR" duration> 6m.. Don't know if i'm clear in my question... Thanks. -- Etienne Roulland <user-318b6b240fb9@xymon.invalid>
list Henrik Størner
▸
On Wed, Apr 06, 2005 at 01:49:45PM +0200, Etienne Roulland wrote:
i'm trying to set rules with multiples conditions like "COLOR=red "and" SERVICE=* "and" DURATION>6m REPEAT=15m RECOVER"
COLOR=red DURATION>6m RECOVERED
MAIL user-47d72ce84f5e@xymon.invalid REPEAT=15m
will do what you want. The rule matching requires that all criteria
are met before a rule matches, so there's an implicit "and" between
each criteria.
"RECOVERED" is actually just a flag - if an alert message was sent
out, then the RECOVERED flag means that a recovery message will also
be sent.
▸
Events are matching if COLOR is RED "OR" duration> 6m.. Don't know if i'm clear in my question...
It would probably help if you run ~hobbit/server/bin/hobbitd_alert --test HOSTNAME SERVICE for the host/service that is causing you headaches, and let us see what the output is. Regards, Henrik
list Thomas Ruecker
Hi, I found some problems with alerts. I had the following sensors in one group: $SENSORS=cisco-cpu,cisco-conn,conn,... In this combination, the will be never an alarm for conn. I changed it to the following: $SENSORS=conn,cisco-cpu,cisco-conn,... And now I get alerts for conn. I think this is a littlebit strange. Thomas
list Tom Georgoulias
▸
Thomas Ruecker wrote:
Hi, I found some problems with alerts. I had the following sensors in one group: $SENSORS=cisco-cpu,cisco-conn,conn,... In this combination, the will be never an alarm for conn. I changed it to the following: $SENSORS=conn,cisco-cpu,cisco-conn,... And now I get alerts for conn. I think this is a littlebit strange.
If you run this command, you can see how hobbit intepreted the alerts file. That might help you point out the problem. ~/server/bin/bbcmd --env=/home/hobbit/server/etc/hobbitserver.cfg hobbitd_alert --dump-config Tom