Let me ommit "cmk --debug -vvn hostname” and just describe my issue.
I’ve set up a rule, that applies label “notify:admin-linux-it” to all hosts and services in “Linux” folder.
When I go to " Monitor > Overview > Service search" and filter services with this label I see all of them listed. So far, so good.
Then I created a notification rule: when service has “notify:admin-linux-it” label send a Slack message to contact group. This also worked as expected. Till today.
And now the issue:
There is built-in check called “Check_MK” - it has the mentioned label as it should, but when it goes CRIT non of the rules match and notify.log says “No rule matched, notifying fallback contacts” and sends an email.
However, two other services I’ve tested (Memory and custom MRPE check) matched the label rule and sends notifications to Slack.
2024-06-03 15:51:02,438 [20] [cmk.base.notify] Global rule 'Slack (services): admin-linux-it'...
2024-06-03 15:51:02,439 [20] [cmk.base.notify] -> matches!
2024-06-03 15:51:02,439 [20] [cmk.base.notify] - adding notification of user1, user2 via slack
My questions are:
is “Check_MK” a kind of special service that will not match any rules?
are there other services that will not match notifications rules when they should?
how to check if all of my services will send notifications as expected (somewhat smarter that “fake test restuts” for ~600 checks)
2024-07-31 15:06:08,756 [20] [cmk.base.notify] Analysing notification (xxxxxxxx_ext;SSH) context with 78 variables
(...)
2024-07-31 15:06:08,757 [15] [cmk.base.notify] Global rule 'Slack (services): logger-admin-linux-it'...
2024-07-31 15:06:08,757 [15] [cmk.base.notify] -> does not match: The service labels {'notify': 'admin-linux-it'} did not match {}
(...)
It sends the fallback email at the end but I would like to get it work correctly.
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.
