[dev.icinga.com #9231] Expose notification period though status api for tools like aNAG to use to only notify you during notification period

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/9231

Created by netmindz on 2015-05-06 13:18:54 +00:00

Assignee: (none)
Status: Rejected (closed on 2015-05-08 08:07:01 +00:00)
Target Version: (none)
Last Update: 2015-05-08 08:07:01 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

---

Currently if you use tools like aNag to be alerted of service or host issues, it can't respect the notification period of that host or service. You can set "global" quiet times in the config of aNag to set quiet times, but if you have a mixture of services that need to be 24/7 but some that are not, there is no way for aNag to know that while this given service is currently in an error state, it it should not notify you.

You can kinda work around this, by setting aNag to never refresh and only trigger a refresh by using NMA, but this doesn't work 100%

Would it be possible to change Icinga2 (and possibly v1 also) to include something in the status result that indicated if this host or service is currently in it's notification window ?

---

Relations:

• duplicates #9235

[icinga-migration]

Updated by ddegois on 2015-05-07 07:52:03 +00:00

May I suggest in_notification_period as boolean in status.cgi hostdetail and servicedetail ?

D.

[icinga-migration]

Updated by mfriedrich on 2015-05-08 08:06:44 +00:00

In Icinga 2 notification objects take care of notification periods, so the exposed status data inside the StatusDataWriter class is not correct at all. We should consider that when implementing the Icinga API where notification objects are accessible as well. I'm closing this feature in favor of #9235

[icinga-migration]

Updated by mfriedrich on 2015-05-08 08:06:53 +00:00

• Duplicates set to 9235

[icinga-migration]

Updated by mfriedrich on 2015-05-08 08:07:01 +00:00

• Status changed from New to Rejected