Werk #22507: Enforced services: no empty item
| Component | Setup | ||
| Title | Enforced services: no empty item | ||
| Date | Oct 8, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
Enforced services are configured as a check plug-in, an item and the parameters. Setup now refuses to save such a rule when the item is empty. The REST API rejects it as well.
An empty item was never meaningful. Service discovery cannot produce such a service, because the plug-in API rejects an empty item, and an enforced one can never find its data: the check plug-in looks its item up in the agent output and an empty item matches nothing there, so the service stays unknown. It is not the same as a service configured without an item either -- its name is rendered from the plug-in's name template with nothing filled in.
Existing rules keep working as before and are not changed by the update. If you have one, the configuration check of "cmk-update-config" reports it as an invalid rule configuration and asks whether to continue. Open the rule in Setup afterwards and enter the item the service is meant to have; which item that is depends on the plug-in -- it is the one the discovered service of the same kind carries.