Nagios Support Forum

OK, so I have a passive service setup like so: The notification interval is 0 as we send them to ticket system and tickets are auto created so only need 1 notification. This particular service has a habit of going bad and then resolving itself so on April 3rd I put that first notification delay of 15 in. Ever since then no notifications have been sent. Today the service was critical for 8 hours and nothing.

Is there a bug/undocumented feature when using both 0 interval and delaying the first notification?

What is check_interval set to? The notification_interval will trigger a notification on the NEXT check if it's value is less than or equal to the check interval value.

This is the configuration on that screen. Notice that active checks are off, this is a passive check that runs every 10 minutes on the host.

Thanks for the update. I initially missed the part where it was mentioned that this was a passive service. I'll set it up to check. Is this a still a 5.6.8 install?

Nope, sorry, need to update signature. 5.6.14!

So the issue here is that notification delays expect at least one more trap to come in(at least 15 minutes later) to be triggered. Without that the notification will not occur.

What we can do is use the freshness check to force a second check X seconds later where X is the notification delay. The freshness check will run check_dummy with the $SERVICESTATEID$ and $SERVICEOUTPUT$ macros which will have the values from the initial passive snmp trap.

But would that freshness check actually ever run? The passive results are coming in every 5 minutes. Let me clarify my issue to make sure I explained it properly.
-----------------------------------------------------------
Host is actively checked for ping every 5 minutes
Host has about 10 services defined on it that are all passive.
nrdp runs every 5 minutes on the host and sends the results back to the XI server.
One of the services is a service check that the service quite often goes down but comes back upon its own in 5 minutes or so, rendering the notifications useless.
Changed delay first notification to 15 to HOPEFULLY result in a delay of 15 minutes so the OK result can be sent in and stop any notifications from being sent.
This has been working great(we thought) until recently when we notices the service check has been critical for over 8 hours.
In those 8 hours the host was sending the passive check results in every 5 minutes, no notification was every triggered
-----------------------------------------------------------

Thanks!

Thanks for the clarification. It wasn't clear that the checks were coming in every 5 minutes. In this case the freshness threshold would not be met. I'll take another look into this with this behavior in mind and let you know what I find.

Hey @cdienger, any update on your findings?

Yes, it looks like it will behave the way you want with the delay if you set it to be a volatile service.