Acknowledgement of 'soft' problems?

[Benoit Panizzon]

> I don't believe that this is supported, and don't know if it ever will
> be. However, why not just have your supporters turn off notifications
> when a host/service goes into a soft state. Then, if it reaches a hard
> state before they can fix it, notifications should not be sent out, and
> they can acknowledge it if they so choose.

Hi Garry

Because they are lazy and don't want to have to click around if they don't 
have to :-)
Often we have Services 'flapping' example: Process monitoring. While reloading 
a very busy nameserver you get two named processes running for a few 
minutes...

If you get two processes permanently something is wrong.

So there need to be three checks for named reporting more than two processes 
to get into 'hard' error status.

But the 'Service Problem' overview already shows the problem while in 'soft' 
state. They don't want to see it.

Or if they know they messed up the DNS they want to acknowledge the problem 
before the pickett get's notified :-)

-- 
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/
------------------------------------------------------------------------


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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