Nagios Support Forum

Having an issue where I'm getting text alerts when I'm pretty sure the notification delays should prevent this from happening. We have a restart service event handler and a notification delay in place to allow for the restart to complete before notifying us of a down service. However still getting alerts for these services then a recovery message shortly after. Here's the alert:
Then I get a recovery like 6 minutes later.

Here's the settings for the service:
And then the host on which the service resides, with the notification delay:

I've even upped the delay to see if it would stop, and it doesn't. This happens with many services on many hosts, configured the same as this. Any insight as to why I get these alerts would be appreciated. Thanks!

What happens when you set "first_notification_delay = 15" on the service itself?

I have not tried this as there are many services on each host and updating all of them would take quite some time. I was under the assumption that "skip" meant that the service inherited the preferences from the host, as there aren't even notification contacts assigned to services, only the hosts themselves.

Actually, the "first notification delay" should be inherited from the service template that is in use (if not specified locally, on the service level).
Go to CCM->Services->View Text Config, to view the config. See what is the service template that is in use (the "use" directive), for example:
Note: There may be a few "layers" of templates. Keep in mind that modifying the template will affect ALL of the services that use it.

OK, so all of these are content monitors, so they are using xiwizard_website_http_content_service

Went into CCM-templates-service templates and made the FND 20 minutes (there's a 3 min delay between stop and start on the event handler, plus a 2 min grace period) for xiwizard_website_http_content_service.

This should fix my issue?

If the rest of the settings are correct for what you are trying to do, it should be fine.

OK, in place since last night and so far so good... I'll keep an eye on it and if I don't get any false alerts in the next couple days I'll assume this fixed it.

Great, we'll keep the thread open.