[EMAIL PROTECTED] schrieb am 02.08.2006 18:04:06: > The problem is that it sounds like you're using scheduled downtimes > incorrectly. It's not meant to be used for *un*scheduled downtimes; thus > the name. It's meant to supress alerts from a machine during the > specified window, and that's exactly what it's doing in your case.
It is a scheduled downtime. I put the host into downtime, because I was planning to reboot it. I do not want notifications to be sent out for the reboot of course, so I am forced to set a downtime. > I can tell you that I'd really annoyed if it didn't work as advertised, > and *did* send alerts in the middle of the night when I was working on a > box and someone else was carrying the pager (well, I might not be the > guy to get annoyed, but I'd hear about it in the morning). I'm not talking about sending alerts. I'm talking about sending recoveries for alerts that happened _before_ the downtime, not for suppressed alerts _during_ the downtime. For those a recovery should never be send of course - as no alert has been sent. > It sounds like you should probably be acknowledging critical services, > rather than marking them as being in scheduled downtime when they're > not. That way the alerts stop until the service comes back up, and > you'll be notified when it changes state. If I acknowledge the problem, everyone get's a notification too. Where's the benefit? And acknowledging the problem doesn't make any difference. Service goes critical SMS gets dispatched Problem gets acknowledged SMS gets dispatched Host gets scheduled for downtime Reboot Host/Service OK Still no notification for the rest of the admins that the service is fixed. For them it looks like it's acknowledged and I'm working on it - but no sign ever that I fixed it. Problem persists and still no progress for me as the outcome stays the same: Noone gets notified that the problem was fixed and people will call if I am still working to fix the problem. I still say: for every WARNING/CRITICAL/UNKNOWN that has be sent there must follow a RECOVERY in case the Service/Host recovers. That's expected behaviour and everything else is rather diffuse behaviour in my opinion. (unless I explicitly suppress all notifications for the service/host in question - but downtime shouldn't work this way) regards Sascha -- Sascha Runschke Netzwerk Administration IT-Services ABIT AG Robert-Bosch-Str. 1 40668 Meerbusch Tel.:+49 (0) 2150.9153.226 Mobil:+49 (0) 173.5419665 mailto:[EMAIL PROTECTED] http://www.abit.net http://www.abit-epos.net --------------------------------- Sicherheitshinweis zur E-Mail Kommunikation / Security note regarding email communication: http://www.abit.net/sicherheitshinweis.html ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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