[Xymon] LOG issues
dewelker at gmail.com
Sat Sep 5 06:53:21 CEST 2015
Martin is right. If you read carefully, all the information is there. It
would just be nice to have more examples indicating what works for wildcard
situations. I was using someone else's posted example, which turned out to
be wrong (or relating to an old way of doing things).
On Fri, Sep 4, 2015 at 1:00 PM, Martin Lenko <lenko99 at gmail.com> wrote:
> I think that this is fairly well documented:
> "logfilename" is the name of the logfile. Only logentries from this
> filename will be matched against this rule. Note that "logfilename" can be
> a regular expression (if prefixed with a '%' character).
> "pattern" is a string or regular expression. If the logfile data matches
> "pattern", it will trigger the "msgs" column to change color. If no "color"
> parameter is present, the default is to go "red" when the pattern is
> matched. To match against a regular expression, "pattern" must begin with a
> '%' sign - e.g "%WARNING|NOTICE" will match any lines containing either of
> these two words. Note that Xymon defaults to case-insensitive pattern
> matching; if that is not what you want, put "(?-i)" between the "%" and the
> regular expression to turn this off. E.g. "%(?-i)WARNING" will match the
> word WARNING only when it is upper-case.
> The thing is that "%" character is not used to match other characters or
> strings in regular expressions. It just instructs Xymon that the following
> string is a regex, not a string value.
> On 4 September 2015 at 17:34, Mark Felder <feld at feld.me> wrote:
>> On Thu, Sep 3, 2015, at 10:35, David Welker wrote:
>> > Found the solution. This works...
>> > LOG %/var/(adm|log)/messages "%named.*?general.*?exiting"
>> > Found it in a 2009 Xymon archive after some serious digging. :)
>> Could the wording in the analysis.cfg man page for LOG be improved in
>> any way?
>> Xymon mailing list
>> Xymon at xymon.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Xymon