We also configure check_logfiles as a volatile service, but that doesn't solve the problem at hand.
I still don't understand how to get Nagios to send notifications until we acknowledge the problem, without ignoring future problems. Can anyone explain if this is possible? -- Jim On Mon, 10 Nov 2008 at 3:04pm, Kyle O'Donnell wrote: > We configure check logfiles as a volatile service and choose not to > use the sticky option. Some logs we configure check-logfiles to send > a message via nsca for each pattern match, ensuring we don't miss any > notifications. We also configure check-logfiles services not to send > out recovery messages, and only schedule downtime or disable > notifications during maintenance. > > On 11/10/08, Jim Winkle <[EMAIL PROTECTED]> wrote: >> We're deploying Nagios (currently using 3.0.2) for our Unix servers, and I >> have >> a question about acknowledgement. >> >> We're using the check_logfiles plugin to monitor syslogs (e.g. >> /var/adm/messages on Solaris). check_logfiles returns CRITICAL when it >> 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 it's possible >> that >> pagers might miss just one page (paging services aren't 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. >> >> My question: Is there a way with Nagios to acknowledge a problem reported by >> a >> plugin like check_logfiles without ignoring future problems? Or would this >> be >> new functionality needed in Nagios? I realize we can syslog an "okpattern" >> string and check_logfiles will then clear, but I'm looking for something >> using >> the Nagios web (and external command_file) interfaces. Using the Nagios >> "Acknowledge" link would be ideal, since that's what folks are going to be >> using for other problems. >> >> Nagios and the check_logfiles plugin are great tools... perhaps I'm simply >> missing something. >> >> Thanks in advance! >> >> -- 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?banner_id=100&url=/ >> _______________________________________________ >> Nagios-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/nagios-users >> ::: Please include Nagios version, plugin version (-v) and OS when reporting >> any issue. >> ::: Messages without supporting info will risk being sent to /dev/null >> > ------------------------------------------------------------------------- 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?banner_id=100&url=/ _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
