Good morning Jim:
You might be interested in reading about volatile services:
http://nagios.sourceforge.net/docs/3_0/ ... vices.html
And, if you use nagios logs for later analysis, you might want to also
look at state stalking:
http://nagios.sourceforge.net/docs/3_0/stalking.html
Thanks, -Jake
-----Original Message-----
From: Jim Winkle [mailto:[email protected]]=20
Sent: Wednesday, November 12, 2008 4:46 PM
To: [email protected]
Subject: [Nagios-devel] Nagios acknowledgement enhancement request
Hi,
I have a suggestion for a future enhancement of Nagios.
In short, I'd like there to be a way to have Nagios send notifications=20
until we acknowledge a problem -- for certain unique plugins -- without=20
ignoring future problems. Background and more details follow.
We're using the check_logfiles plugin to monitor syslogs (e.g.
/var/adm/messages on Solaris). check_logfiles returns CRITICAL when it=20
detects a problem, but then normally clears itself (returns OK) the next
time it runs. Nagios notifies us only once under this scenerio, and
since=20
it's possible that pagers might miss just one page (paging services
aren't=20
100% reliable), we'd rather get notified until we explicitly acknowledge
the problem.
The check_logfiles plugin does have the capability to continue to report
the
error (using its "sticky" option). This is good since then we're
notified
longer, but if we then use the Nagios "Acknowledge" link to acknowledge
the
problem, new problems (e.g. new errors in /var/adm/messages) reported by
the
check_logfiles plugin get ignored.
I asked on the nagios-users list if there was a way to acknowledge a
problem=20
reported by a plugin like check_logfiles without ignoring future
problems.=20
Nobody came up with a way, so I assume this is new functionality needed
in=20
Nagios.
I realize we can syslog an "okpattern" string and check_logfiles will
then=20
clear, but I'm looking for something using the Nagios web (and external=20
command_file) interfaces. Using the Nagios "Acknowledge" link would be
ideal,=20
since that's what folks are going to be using to acknowledge other
problems.
I'm using Nagios version 3.0.5 and check_logfiles version 2.4.1.3. We
configure=20
check_logfiles as a volatile service and use state staulking.
Thanks for providing these great tools! Please let me know if something
doesn't=20
make sense or if I'm missing something.
-- Jim
------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php? ... 00&url=3D/
_______________________________________________
Nagios-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/lis ... gios-devel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: im Winkle [mailto:[email protected]]=2