[dev.icinga.com #13953] Introduce "cost" to NotificationComponent

[icinga-migration]

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

Created by twidhalm on 2017-01-12 09:16:43 +00:00

Assignee: (none)
Status: Rejected (closed on 2017-01-13 08:27:51 +00:00)
Target Version: (none)
Last Update: 2017-01-13 08:27:51 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

---

Hi,

I've seen some customers running Icinga 2 Masters with different connections for notifications. While this might not be a problem with Internet uplinks there might be a big difference with SMS Gateways / Sticks. Some users can't afford to have several flatrate SMS plans so they want to have a way of defining primary and secondary senders of notifications. The primary sender would have a flatrate and others would have some sort of cheaper plan.

I could imagine an option to set primary and secondary notification senders or, maybe even better, a "cost" option which would work as a priority when determining which host to use when sending notifications.

Cheers,
Thomas

[icinga-migration]

Updated by mfriedrich on 2017-01-13 08:27:51 +00:00

• Status changed from New to Rejected

As discussed offline, this involves a historical track of notifications including cluster replication and more. I like the idea about I think this will become overly complicated inside the core. Such a thing should be dealt with external addons such as NoMa. Eric has been informed, I am therefore closing this request.