views:

192

answers:

1

We are using Nagios to monitor our network with great results. There is now a new requirement we are struggling with:

  • We want to notify Nagios of an non fatal but critical application errors. The application does not stop running but there is some sort of issue that needs looking into.

  • Once the issue has been looked into, we need some way to "unflag" the issue in Nagios.

We tried using the syslog, but the biggest problem was once an error was logged, the service was put into an error state with no way to recover. Also, while applications would report a critical error to the syslog, most of the time they don't report an "All clear" error.

A: 

I've done this using passive checks: http://nagios.sourceforge.net/docs/2_0/passivechecks.html

Basically, you're application is just going to feed the nagios core some data into its external command file. Nagios will eventually read the data and update the alerts, execute event handlers, etc.

Exactly how you set this up will be unique for your case, but if you need any other help just let me know. :)

gnucom