Werk #19806: Service discovery: Disabled services are no longer written to autochecks via the discovery backend
| Component | Checks & agents | ||||
| Title | Service discovery: Disabled services are no longer written to autochecks via the discovery backend | ||||
| Date | May 7, 2026 | ||||
| Level | Prominent Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
Werk 19800 prevented services matched by a Disabled services rule from being written to the autochecks file via the WATO Accept all action, with the framing that "only monitored services are supposed to be written to that file".
The same rule did not yet apply to the autodiscovery backend. Disabled services were still persisted to autochecks when the discovery automation ran, e.g. via the interactive Remove all and find new action, the bulk discovery, or the periodic discovery.
This werk aligns the autodiscovery backend with werk 19800: services classified as ignored (matched by a Disabled services rule) are no longer written to the autochecks file by the discovery automation. The disabled-services rule itself remains in place, so re-enabling the service later will re-discover it normally.
The behaviour for clustered services on a node that is mapped to a cluster (transition clustered_ignored) is unchanged.