Catch up on the latest product updates, best practices, and expert insights from the Checkmk Conference #12 – Watch the livestream recordings now

Werk #19724: "Do not match Event Console alerts" matched only Event Console alerts

Component Notifications
Title "Do not match Event Console alerts" matched only Event Console alerts
Date Aug 10, 2026
Level Prominent Change
Class Bug Fix
Compatibility Incompatible - Manual interaction might be required
Checkmk versions & editions
3.0.0b1
Not yet released
Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT
2.5.0p13
Not yet released
Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT
2.4.0p37
Not yet released
Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT

Notification rules configured to not match Event Console alerts did not exclude them. What such a rule matched instead depended on its other event conditions:

  • Without any host or service event condition, the rule did the exact opposite of the option: it matched Event Console alerts only, and stopped matching host and service notifications.
  • With a host or service event condition, the option had no effect at all. Event Console alerts were treated like any other service notification and kept matching the rule whenever their state change matched its service events.

This is a regression introduced in Checkmk 2.4.0p10 by Werk #18082, which reworked Event Console alert matching without covering this option. Matching is now correct again: such rules exclude Event Console alerts and match host and service notifications as configured by their other conditions.

Affected are rules created before Checkmk 2.4, rules for users and personal notification rules, and rules created via the REST API with conditions.event_console_alerts.value.match_type set to do_not_match_event_console_alerts. Since match_host_event_type and match_service_event_type are enabled by default, a rule created via the REST API without explicitly disabling both of them falls into the second case above.

Such a rule also no longer opens in the notification Quick Setup with an empty "Specific events" selection that could not be saved. It now shows all host and service events with "Event Console alerts" unselected, which is equivalent. Note that saving the rule there stores that explicit event selection, so the REST API reports event_console_alerts as disabled afterwards.

Please review notification rules that use this option. Depending on their other event conditions, they may now send host and service notifications that were suppressed before, and they no longer send notifications for Event Console alerts.

To the list of all Werks