The event handler might work but doesn't it stop executing after the service enters a hard state? 0 (At least, that's how I understood nagios 2.x to work, perhaps nagios 3.x differs in this regard.)
A clever workaround to this might be to use the performance processing options built into nagios. Perhaps by using the 'service_perfdata_command' and 'process_performance_data' nagios options, and the 'process_perf_data' service directive, you could call a script to process the data, log to a database, send emails, etc. This is not 100% ideal, since nagios should be handling the notifications/emails. Instead of sending the emails, the above said script could also submit a 'critical' passive check to a single volatile service if the status is critical AND has changed... but at this point I think I'm making this more complicated than it needs to be. -Aaron Patrick Morris wrote: > Why not use an eventhandler that parses the plugin output? > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > 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 DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ 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
