:-) I did the same thing when I first changed our alerting, was swearing
at it for a while then realised, still reduced 20 conditions to 9 so all
worked out in the end.
Jason.
From: Geoff Hallford [mailto:user-dc9e7f30b1e2@xymon.invalid]
Sent: 07 November 2006 13:55
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Problem with Regular Expression in Alert
Yes, that did it. For some reason didn't think of making the whole thing
a regex.
Thank you.
On 11/7/06, Jones, Jason (Altrincham) <user-ee957b46acd2@xymon.invalid> wrote:
This should work: COLOR=red EXSERVICE=%(msgs|^int.*)
Jason.
From: Geoff Hallford [mailto:user-dc9e7f30b1e2@xymon.invalid]
Sent: 07 November 2006 13:30
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] Problem with Regular Expression in Alert
Hi Everyone,
I am having an issue where Hobbit will not take multiple alert
parameters if one of them is a regular expression. I have my hobbit
built with MRTG integration. My example is that I want to have my catch
all rule exclude all msgs and interfaces (in the format int01-08,
int09-16, ...).
This works: COLOR=red EXSERVICE=%^int.*
This doesn't work: COLOR=red EXSERVICE=msgs,%^int.*
Does anyone have any hints, how to get this working? Maybe even a
logical approach to get it working and not necessary a technical
approach?
Thanks.
--
'If my answers frighten you then you should cease asking scary
questions.' --Sam Jackson from Pulp Fiction