Werk #22108: Service discovery: cmk -I and cmk -II now apply the same filters as the other discovery entrypoints
| Component | Checks & agents | ||
| Title | Service discovery: cmk -I and cmk -II now apply the same filters as the other discovery entrypoints | ||
| Date | Aug 28, 2026 | ||
| Level | Prominent Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
The commandline service discovery (cmk -I and cmk -II) was the only one of the four
discovery entrypoints that did not route through the shared transition-table layer. As a
result it skipped several semantic filters that the interactive discovery, the bulk discovery
and the periodic discovery all apply, so cmk -I/cmk -II could leave the autochecks file in
a state that the other entrypoints would never produce.
Concretely, the following divergences are now fixed:
- Disabled services: services matched by a Disabled services rule were written to the
autochecks file by
cmk -I/cmk -II. In line with werk 19806, such services are no longer persisted. - Enforced services: a discovered service that is shadowed by an enforced (static) check was kept as a redundant autocheck entry. It is now dropped, as the enforced check already covers it.
- Disabled checks: an autocheck of a check plug-in that had meanwhile been disabled was kept
by
cmk -Iinstead of being removed. Such stale entries are now dropped.
The commandline discovery now behaves consistently with the interactive Accept all /
Remove all and find new actions and with the automatic discovery. cmk -I still only adds
newly discovered services and leaves existing ones untouched, while cmk -II still removes
vanished services and adopts changed parameters and labels.
The --plugins/--checks plug-in restriction and the --only-host-labels mode keep working
as before: services of plug-ins that were not selected are left alone.