Opentelemetry Collector K8S
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 2/stable | 162 | 08 Apr 2026 | |
| 2/stable | 163 | 08 Apr 2026 | |
| 2/candidate | 174 | 21 Apr 2026 | |
| 2/candidate | 173 | 21 Apr 2026 | |
| 2/beta | 174 | 21 Apr 2026 | |
| 2/beta | 173 | 21 Apr 2026 | |
| 2/edge | 174 | 17 Apr 2026 | |
| 2/edge | 173 | 17 Apr 2026 | |
| dev/edge | 180 | 20 Apr 2026 | |
| dev/edge | 179 | 20 Apr 2026 | |
| 1/stable | 32 | 06 Aug 2025 | |
| 1/stable | 31 | 06 Aug 2025 | |
| 1/candidate | 32 | 06 Aug 2025 | |
| 1/candidate | 31 | 06 Aug 2025 | |
| 1/beta | 32 | 06 Aug 2025 | |
| 1/beta | 31 | 06 Aug 2025 | |
| 1/edge | 32 | 14 May 2025 | |
| 1/edge | 31 | 14 May 2025 |
juju deploy opentelemetry-collector-k8s --channel dev/edge
Vendor-agnostic way to receive, process and export telemetry data.
OpenTelemetry Collector K8s is a Juju charm that deploys and manages the OpenTelemetry Collector on Kubernetes, providing a vendor-agnostic telemetry pipeline for receiving, processing, and exporting metrics, logs, traces, and profiles. It is a component of the Canonical Observability Stack (COS): https://documentation.ubuntu.com/observability
The collector aggregates telemetry from related charms and forwards it to the appropriate backends such as Prometheus, Loki, and Tempo through Juju relations.
Key features:
- Vendor-agnostic telemetry collection covering metrics, logs, traces, and profiles in a single workload.
- Native OTLP ingestion (gRPC/HTTP) as the primary protocol, with additional support for Jaeger and Zipkin.
- Automatic scraping of Prometheus metrics endpoints from related charms.
- Forwarding of telemetry to COS backends — Prometheus (remote write), Mimir, Loki, and Tempo — through Juju relations.
- Built-in Grafana dashboards for self-monitoring.
- TLS support with configurable CA trust via the receive-ca-cert and receive-server-cert relations.
- Ingress support for cross-model telemetry collection through Traefik.
- Configurable processors, sampling rates, and scrape intervals.
- Grafana Cloud integration via the cloud-config relation.
- Persistent storage for telemetry data durability across container restarts.
- Configurable Kubernetes resource limits for CPU and memory.