On 07.01.2014 12:58, Uwe Schuerkamp wrote:
Hi folks,
we've been running into "problems" with icinga not sending out
notifications to all contacts / contact groups until the
notification_interval expires.
Background: A service has two contact groups with different
notification periods. One group receives mails 24x7, while the other
gets notified by pager during workhours, say 0900 - 1700 during the
week.
What's happening now: If a service goes down at 0800, the mail group
is notified. However the second (pager) group, whose notification
period starts an hour later, won't get notified until the expiry of
the notification_interval (usually 4 hours in our case).
What I would like to happen: If a configuration variable is set (say
"notify_at_beginning_of_notification_period=1"), icinga sends out
notification to each contact group that has not been notified yet at
the beginning of their respective notification interval.
I'm not sure if anyone would actually *want* that to happen. If a
problem persists in its problem state, but does not match the current
notification period, those contacts shouldn't be notified afterall.
I would re-think the strategy of setting a notification_interval to 4
hours instead. Why don't you set the 24x7 group to their local
notification_interval of 4 hours, and let the general service
notification_interval happen every hour?
Implementing it this way would not break backwards compatibility or
change the icinga behaviour unexpectedly.
I highly dislike additional config options used for such specific cases,
changing the way notifications are handled, hardening the way to debug
the core. The state based escalation ranges weren't the best idea, nor
were the empty hostgroup assignments.
Also, from what I've read about them, escalations won't really help
here in the way they are currently implemented.
Your root problem seems to be the service's notification_interval being
4 hours. That "filter" makes it impossible for lower intervals on a
contact basis.
Regards,
Michael
--
DI (FH) Michael Friedrich
mail: michael.friedr...@gmail.com
twitter: https://twitter.com/dnsmichi
jabber: dnsmi...@jabber.ccc.de
irc: irc.freenode.net/icinga dnsmichi
icinga open source monitoring
position: lead core developer
url: https://www.icinga.org
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
