---
title: Charmhub | Deploy Opentelemetry Collector K8S using Charmhub - The Open Operator
  Collection
description: Deploy the latest version of Opentelemetry Collector K8S as a Kubernetes
  Operator on any cloud. Vendor-agnostic way to receive, process and export telemetry
  data.
url: https://charmhub.io/opentelemetry-collector-k8s
---

# Opentelemetry Collector K8S

[Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

* [Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

Platform:

0.130/stable rev270-1-gc06dfe8

```
juju deploy opentelemetry-collector-k8s --channel 0.130/stable
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

[Read documentation](https://documentation.ubuntu.com/observability/latest)

#### Contacts

* [Submit a bug](https://github.com/canonical/opentelemetry-collector-k8s-operator/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

#### 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.