CMK version:2.3p3 Cloud Edition
OS version:Almalinux 9
Error message: → does not match: The service level 0 is not between 30 and 30.
The error message is the output from var/log/notify.log
So I have notifications rules that trigger services of the Service Level 30 (Platinum) when going to critical. But i get the error above when testing.
This was working in 2.2 but after upgrade it does not work.
Anyone seen anything like this before?
Hi Sune,
does the affected service show the correct service level in the service view table ?
Starting think i need to create a bug report on this one.
Update to 2.3.0p2
→ Matches this service and does not match for others
You are really sure it’s a service from your adjusted view?
I will just try this.
Configure a service level (30) on a service.
Apply config.
The do a manual test.
output from var/log/notify.log
Still no cigar.
Might this issue be connected with my notification problem?
One possible problem could be that the “Test notification” has not all the variables like a normal notification.
Normal notification
I don’t know that SL variable is evaluated inside the notification rules.
hmm @andreas-doehler could be the case when testing, But it does not seem to work under normal circumstances either.
I will continue to try and find the reason.
In my case the test is working.
Assigned SL 20 to the services.
Got one event as shown in my screenshot above.
The notification rule has only the SL condition.
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.
