If a notification plugin fails, cmk usually shows a red box on the right sidebar on the dashboard, letting you know that N notifications have failed. You can then review and acknowledge the failed notifications and try to fix the problem. That’s at least what 2.3 did.
However I experienced that - for some reason I unfortunately can’t pinpoint - it is possible for the new notification_parameters you set in 2.4 to reference a parameter “object” that does not exist. In this case, if you edit the rule, the parameters dropdown will tell you No options available, but it is referencing something - you can see that because the Edit button is not greyed out:
If you click edit, you’ll also get the UUID of the missing parameter set:
There may or may not be a bug leading to this scenario, but I’ve created this thread because if this happens, notifications fail silently. notify.log then looks like this:
2025-06-13 12:41:34,014 [20] [cmk.base.notify] ----------------------------------------------------------------------
2025-06-13 12:41:34,014 [20] [cmk.base.notify] Got raw notification (somehost;CS GF: eu1/c51/server9) context with 54 variables
2025-06-13 12:41:34,015 [20] [cmk.base.notify] Global rule 'myrule'...
2025-06-13 12:41:34,015 [20] [cmk.base.notify] -> matches!
2025-06-13 12:41:34,015 [20] [cmk.base.notify] - adding notification of Jay2k1 via discord.py
2025-06-13 12:41:34,015 [40] [cmk.base.notify] ERROR:
Traceback (most recent call last):
File "/omd/sites/monitoring/lib/python3/cmk/base/notify.py", line 492, in locally_deliver_raw_context
return notify_rulebased(
^^^^^^^^^^^^^^^^^
File "/omd/sites/monitoring/lib/python3/cmk/base/notify.py", line 776, in notify_rulebased
notifications, rule_info = _create_notifications(
^^^^^^^^^^^^^^^^^^^^^^
File "/omd/sites/monitoring/lib/python3/cmk/base/notify.py", line 888, in _create_notifications
parameters[plugin_name][plugin_parameter_id]["parameter_properties"]
~~~~~~~~~~^^^^^^^^^^^^^
KeyError: 'discord.py'
2025-06-13 13:51:35,023 [20] [cmk.base.notify] ----------------------------------------------------------------------
I’ve had this with telegram notifications as well. I had to switch to a different telegram plugin for notifications after updating to 2.4 because the mkp I was using was incompatible, so I switched to the one used in your blog post and added two notification parameter objects (for two contacts) as as per its readme and sent a few test notifications, which worked.
Some time after, the parameter objects apparently disappeared (which I’ve just discovered the other day) - same issue and symptoms as mentioned above.
Should I figure out how to repro the disappearing options, I’ll update this post, but for now, the main issue is that currently, whenever this happens, notifications fail silently which I think is bad.
I am using CRE 2.4.0p4 on Ubuntu 24.04 LTS.