Hello Timo, > Here are the log entries: Well in your case everything works as it should.
Let me explain the flow: * Service gets critical * Notification to icingaadmin is sent out * Downtime starts * Service recovers * Notification to icingaadmin and you is sent out * Downtime ends The recovery is sent out because the service had a critical state before the downtime began. Only upcoming alerts during the downtime are suppressed. If a service stays critical when the downtime ran out an alert will be sent by then. On the other hand, the reason why you received the recovery is because it happens during your notification_period. The logic is simple, an error happens at daytime, is acknowledged, but can only be fixed at night when you are responsible. Dayshift is notified when the service gets critial, nightshift when it gets recovered. The shift handover should happen on Layer 8 :-) Regards Markus -- Markus Frosch mar...@lazyfrosch.de http://www.lazyfrosch.de ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
