Werk #20041: Enforced services: apply service labels from rulesets in monitoring
| Component | Core & setup | ||||
| Title | Enforced services: apply service labels from rulesets in monitoring | ||||
| Date | Jul 21, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
Previously, service labels assigned via the Service labels ruleset were not applied to enforced services (also known as static or manual checks) in monitoring. The labels were shown when viewing the service parameters on the service discovery page, but they were missing from the monitored service, so they could not be used for filtering, views, or label-based rule matching.
This has been fixed. Enforced services now receive their ruleset-assigned service labels in monitoring, just like discovered services do.
This is a regression that was introduced in Checkmk 2.5.0; version 2.4.0 was not affected.
Technical background
When building the check table, enforced services were created with an empty label set and never evaluated the Service labels ruleset, whereas discovered services and clustered enforced services computed their effective labels correctly. The service discovery page still displayed the labels because it computes them independently, which is why the labels were visible there but not in monitoring.