Werk #19141: REST API: configure the OpenTelemetry integration (unstable)
| Component | REST API | ||||
| Title | REST API: configure the OpenTelemetry integration (unstable) | ||||
| Date | Jul 9, 2026 | ||||
| Level | Prominent Change | ||||
| Class | New Feature | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
You can now automate the configuration of the OpenTelemetry integration via the REST API. The endpoints are published in the unstable version of the API so that we can gather feedback before committing to a stable interface.
The following endpoint families are now documented and available in the embedded API documentation at Help → REST API → Documentation (remember to switch to the unstable version):
- Open Telemetry / Receivers - list, show, create, update and delete the receiver configuration of the OpenTelemetry collector.
- Open Telemetry / Prometheus scrape - list, show, create, update and delete the Prometheus scraping configuration.
- Open Telemetry / Collector - enable the OpenTelemetry collector and read its current state.
- The metric backend enablement endpoint, so you can enable the metric backend and read its status.
- The Dynamic Configuration Daemon (DCD) for Metric Backend connection endpoints, so you can create, list, show and delete DCD connections that use the metric backend connector.
Concurrent modifications are guarded with ETag headers on the endpoints that
support them, following the same conventions as the rest of the REST API.
Unstable
These endpoints are part of the unstable API version. They may change or be removed in a future release without a compatibility werk. Use them for experimentation and to give us feedback; do not rely on them for long-lived automation yet.
Not included
The OpenTelemetry Quick Setup (configuration "bundle") endpoints are intentionally not part of this publication and remain on the internal API version.