# Icinga Notifications handling disabled check

**URL:** <https://community.icinga.com/t/icinga-notifications-handling-disabled-check/14638>\
**Category:** Icinga 2\
**Tags:** notifications\
**Created:** [February 27, 2025, 8:44am UTC](https://community.icinga.com/t/icinga-notifications-handling-disabled-check/14638 "2025-02-27T08:44:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rikustm](https://community.icinga.com/letter_avatar_proxy/v4/letter/r/6f9a4e/32.png) [@rikustm](https://community.icinga.com/u/rikustm)\
**Post date:** [February 27, 2025, 8:44am UTC](https://community.icinga.com/t/icinga-notifications-handling-disabled-check/14638/1 "2025-02-27T08:44:43Z")

</div>

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

 ![Screenshot 2025-02-27 at 09.32.45](https://community.icinga.com/uploads/default/original/2X/6/64650aced1368d93bad0ebdc410a5ca807069292.png)

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](https://icinga.com/blog/icinga-notifications-incidents-escalations-and-event-rules/))

Any advice will be appreciated.  
Regards, Rikus

---

<div class="post-metadata">

**Author:** ![apenning](https://community.icinga.com/user_avatar/community.icinga.com/apenning/32/7669_2.png) [@apenning](https://community.icinga.com/u/apenning)\
**Post date:** [February 27, 2025, 9:39am UTC](https://community.icinga.com/t/icinga-notifications-handling-disabled-check/14638/2 "2025-02-27T09:39:25Z")

</div>

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/03-Configuration/#command-transport-configuration)
- [https://icinga.com/docs/icinga-db-web/latest/doc/04-Security/#permissions](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/01-About/#big-picture)
- [https://icinga.com/docs/icinga-notifications/latest/doc/20-HTTP-API/#process-event](https://icinga.com/docs/icinga-notifications/latest/doc/20-HTTP-API/#process-event)
- [https://icinga.com/blog/icinga-notifications-custom-sources/](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.

---

<div class="post-metadata">

**Author:** ![rikustm](https://community.icinga.com/letter_avatar_proxy/v4/letter/r/6f9a4e/32.png) [@rikustm](https://community.icinga.com/u/rikustm)\
**Post date:** [February 27, 2025, 10:59am UTC](https://community.icinga.com/t/icinga-notifications-handling-disabled-check/14638/3 "2025-02-27T10:59:58Z")

</div>

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