Label-Based notification rules ignored for active checks (http-checks)

CMK version: Checkmk Raw Edition 2.3.0
**OS version: Ubuntu 22.04 (Dockerized environment) **

Error message:
Recently I noticed that active checks do not seem to trigger my notification rules correctly.

My setup looks like this:
-specific hosts get the host label: “notify:sms”
-all services of which the host has the host label “notify:sms” inherit the service label “notify:sms”

The “notify:sms” label triggers my notification rules: “SMS Notifications Hosts” or “SMS Notifications Services” depending on it being a host or service.

This works very well for all passive checks which are discovered by SNMP or other checks like “NetApp via Ontap REST API”

However, I noticed this setup doesn’t seem to work with active checks such as HTTP Checks even though the checks seem to have inherited the labels and contact group correctly. Furthermore, the CheckMK-Checks (such as Check_MK and Check_MK Discovery" seem to ignore the rule as well.

Here’s an example:
-I tested the HTTP Check named “HTTPS Confluence”. The service does have the label “notify:sms”.
-The only rule matching according to the “test notifications” is “Mail for ALL Hosts and Services” though. (This rule is supposed to catch all hosts and services and send out Mails - so this is correct behavior):

Hoewever, “SMS Notifications Services” does not match, even though the service itself does have the service label “notify:sms”

As mentioned before, passive checks do not have this problem and the rule does match:


Did anyone else encounter this problem? Is this a bug?
Does anyone have a solution on how to automate notifications consistently without using the labels, if this is indeed a bug?
At the moment I just create new notification rules for all active checks I created. But it is rather tiresome and prone to mistakes to manually edit all notification rules for all active services.

What version do you use exactly?
Currently i’m not able to reproduce this in the latest CRE release.

Can you hover over this one, is the reason really the missing service label?
image

Hi, as of now I’m using Checkmk Raw Edition 2.3.0 (no sub-version)

yes, unfortunatly it is:

Please update to the latest version, it may be related to this werk

thank you. I am currently using the docker image: checkmk/check-mk-raw:2.3.0-latest. I came to understand that this is the latest 2.3-version, is it not?

I tried changing to checkmk/check-mk-raw:2.3.0p10 and to checkmk/check-mk-raw:latest. However, when starting my container with these images the container is stuck in “restarting”.

“docker logs checkmk” shows these messages:
-### UPDATING SITE
/docker-entrypoint.sh: line 113: omd: command not found
-### PREPARE POSTFIX (Hostname: 869e76145a4f, Relay host: postfix_container)
-### STARTING MAIL SERVICES
869e76145a4f syslogd: /dev/xconsole: No such file or directory
postfix/postfix-script: starting the Postfix mail system
…done.

checkmk/check-mk-raw:latest should be the correct one. I understood that you use 2.3.0 (without a patch level)

do you have any idea why I might be getting error messages when switching from checkmk/check-mk-raw:2.3.0-latest. to checkmk/check-mk-raw:latest?

-### UPDATING SITE
/docker-entrypoint.sh: line 113: omd: command not found

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.