Icinga Notifications handling disabled check

[rikustm (Rikus)]

The new Icinga Notifications module does not seem to honour when notifications for a service/host is disabled in Icinga Web.

Even if notification is disabled for a check, it still gets picked up in the Notifications module and sends out a notification message.

Is there a way to filter out such events in the Notification Event Rules or any other way to achieve this? Event Rules only seem to support filtering by host/service groups. (Icinga Notifications: Incidents, Escalations, and Event Rules)

Any advice will be appreciated.
Regards, Rikus

[apenning (Alvar)]

Thanks for posting and please excuse the confusion.

These Feature Commands are part of Icinga DB Web, allowing to alter the Icinga 2 Host or Service object.

• https://icinga.com/docs/icinga-db-web/latest/doc/03-Configuration/#command-transport-configuration
• https://icinga.com/docs/icinga-db-web/latest/doc/04-Security/#permissions

Thus, if you toggle the Notifications feature, this only relates to the Icinga 2 Notifications, but not the new Icinga Notifications project, allowing also other notification sources outside of Icinga 2.

• https://icinga.com/docs/icinga-notifications/latest/doc/01-About/#big-picture
• https://icinga.com/docs/icinga-notifications/latest/doc/20-HTTP-API/#process-event
• https://icinga.com/blog/icinga-notifications-custom-sources/

Again, please excuse the confusion. We should definitely look into this to unify these things, e.g., synchronize the altered notification state from Icinga 2 to Icinga Notifications.

[rikustm (Rikus)]

Thank you for the reply and good to see it is on the radar.