How to handle 'single bad' or 'trap' messages?

[Benoit Panizzon]

Hi

We have the requirement of handling what I call a 'single bad' message.

When such an event happens, somebody would need to aknowledge the message and 
the status should turn to OK.

Example:

We monitor a logfile and get a message about say, memory corruption. This 
message stays in the logs, it's not going to be fixed, so it's being alerted 
as critical.

But as soon as a tech has seen this message, he should be able to aknowledge 
it, order new memory and the message should turn green again.

Antoher example: The backup software tells us that one host could not 
successfully be saved. => Alert. Tech in duty takes a look, acknowledges the 
problem. => ok.

Does somebody have a solution how to implement that in nagios?

Regards
-- 
Benoît Panizzon, <bp at imp.ch>
------------------------------------------------------------------------
ImproWare AG, UNIXSP & ISP                     Phone: +41 61 826 93 00
Zurlindenstrasse 29                            Fax:   +41 61 826 93 01
CH-4133 Pratteln                               Net:   http://www.imp.ch/
------------------------------------------------------------------------


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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