Nagios Support Forum

yes, i would still like to get a solution for my problem...but since i understand that there is non without starting to spam contacts with the same problem you might as well close this topic.

The only solution (rather workaround) that I can think of, is to duplicate the service, add the contacts with the "custom" time period (06:00-24:00) AND use the same period as the notification_period for the service. When the notification period is set on the service level, Nagios Core won't be sending any notifications for any issues that happened before 6:00, but it will send them at 6:00. This way, your contacts will receive a non-OK notification in the beginning of their timeperiod before receiving a recovery.

I understand that this option may not be suitable for large environments - no one wants to duplicate bunch of services, and increase the load on the server, while monitoring the same thing. If you however had only a few "critical" services, you could implement this workaround.

I talked to our developers, and discussed the possibility for adding an option in Nagios XI for sending the non-OK notifications for issues that happened before the contact's notification period when the timeperiod starts. Not everyone would want to use this option, because most people do not use notification_period=0, but prefer to get notified at some interval. It would be nice to have it though in case you want to use it. I am not sure when/if this is going to be implemented - just wanted to give you heads up that we are looking into it, and discussing various options.

Thank you!

Thank you!