Bug #2832: Notification delay can lead to OK notifications without prior CRIT notifications

Date: 2015-12-11State: openClass: nastinessComponent: core

If you use first notification delay and during the delay phase a servicegoes OK again then the core has no knowledge whether a notification for CRITalready has been sent. It always sends the OK notification. Can we fix thisand safely determine wether CRIT was alarmed and thus needs to be mirroredby an OK notification? Maybe by using some timestamp?