On Wed, Aug 20, 2008 at 1:56 PM, Thomas Guyot-Sionnest <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 20/08/08 04:47 AM, Mikael Fridh wrote: >> On Wed, Aug 20, 2008 at 9:46 AM, Marcus <[EMAIL PROTECTED]> wrote: >>> >>> >>> How about integrating a trouble-ticket, so no catastrophes are missed >>> anymore? >> >> I'm thinking if you're the one deciding when the service is OK or not, >> and not Nagios: >> ACK + disable active checks until you're done. >> >> That way there would be no flapping of the service, it will be >> considered and logged as DOWN until you decide it's working. > > Personally I prefer disabling notifications, so I can still see state > changes going on. I don't have flapping detection enabled neither.
Yes, it's up to personal or site preference. > Another method is using scheduled downtimes; that way you can't forget > to re-enable the service. A problem could be it would then count as just that in the statistics - scheduled downtime, which it is not. -- Fridh ------------------------------------------------------------------------- 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 Nagios-users@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
