Werk #20205: Rename the metric backend to data backend and telemetry metrics
| Component | Site management | ||
| Title | Rename the metric backend to data backend and telemetry metrics | ||
| Date | Sep 7, 2026 | ||
| Level | Prominent Change | ||
| Class | New Feature | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
The ClickHouse based storage introduced as the "metric backend" is now split into two consistently named parts. The storage and its configuration are called the data backend. The OpenTelemetry ingestion and querying features built on top are called telemetry metrics.
This werk collects the resulting user-visible renames. No stored configuration needs to be migrated: persisted identifiers keep their values, only display names change. The exceptions are the OMD service and site binaries, which are renamed as described below.
What changed
Site services and binaries
- The OMD service
metric-backendis nowdata-backend, soomd start|stop|status data-backendand itsetc/init.dandetc/rc.dentries use the new name. - The site binaries
cmk-metric-backend-schema-managerandcmk-monitor-metric-backendbecomecmk-data-backend-schema-managerandcmk-monitor-data-backend. - The OMD update and restore hooks that upgrade or recover the database schema are renamed accordingly.
- The self-monitoring service
OMD <site> metric backendis nowOMD <site> data backend.
Display names in the GUI
- The global setting, the backup domain, the sidebar element and the disk-usage graph now read "data backend".
- The custom graph query permission, the custom query rule set, the custom graph data source and the DCD connector type now read "telemetry metrics".
- The architecture documentation and the man pages follow the same split.
What you need to do
If your own scripts call omd ... metric-backend or cmk-metric-backend-schema-manager, switch to the new names.
cmk-metric-backend-schema-manager stays for one release as a deprecated wrapper around cmk-data-backend-schema-manager; the OMD service name has no such wrapper.
omd update replaces the init script and rc link, so an enabled data backend comes up under the new name on its own.
A locally modified etc/init.d/metric-backend is offered for merge as usual.
The self-monitoring service is rediscovered under its new name on the next service discovery.