Bug#298495: [Logcheck-devel] Bug#298495: logcheck-database: add nagios unreachable filter

[maximilian attems]

tags 298495 pending
thanks

On Wed, 23 Mar 2005, Geoff Crompton wrote:

> I only sent UNREACH examples, because those are the only lines that are 
> showing up in my logcheck emails from nagios, (apart from ones that I 
> should see, like nagios stoping or starting). The rest are already 
> matched in /etc/logcheck/ignore.d.server/nagios.
> I also gave you the '.*' rule in my patch because thats what the other 
> rules in /etc/logcheck/ignore.d.server/nagios were doing.
> The problem with nagios filtering is that all these lines are generated 
> by plugins, so there is a huge variety of potential strings. In my mind, 
> once you have matched upto that point, it doesn't matter what the rest 
> of it says, but only because that information gets reported in other 
> places (on the nagios web interface, sent via emails or pagers if 
> configured). So the fact that an admin may not see it in a logcheck 
> email doesn't matter, a user of nagios is using nagios precisely so they 
> get alerted about these things in the way they choose.
> What are your thoughts on this?

agreed,
thanks for your info hadn't look at this rule for some time now.

added to current logcheck cvs, will be in next release:
^\w{3} [ :0-9]{11} [-._[:alnum:]]+ nagios: HOST ALERT:
[._[:alnum:]-]+;UNREACHABLE;(SOFT|HARD);.*$


--
maks