OpenTelemetry

OpenTelemetry (OTel) is a framework for collecting logs, metrics, traces and other signals. It defines a common data model for the signals, a transport protocol, a set of naming conventions and a set of software components that implement them.

OpenTelemetry is not a backend, a database or a visualization tool: you send the data to Elastic, Grafana, ClickHouse, Datadog or whatever fits your stack best. The goal is to eliminate vendor lock-in and unify the way telemetry is collected and transported. In concrete terms, it promises that you can change the observability database or console without redoing the instrumentation.

The strengths: vendor neutrality and the freedom to switch backends with a single instrumentation. The limits: complexity, an evolution driven by committees, and a maturity that differs from component to component.

Incremental adoption

In real projects I tend to apply an incremental approach:

  1. Setting up the collection infrastructure. Installing the OpenTelemetry Collectors and choosing the backend.
  2. Collecting the existing telemetry. Collecting the logs and metrics that virtual machines and Kubernetes clusters already produce, without touching the application code.
  3. No-code instrumentation. Applications are instrumented with the OpenTelemetry automatic agents, which produce traces and metrics without changes to the source.
  4. Instrumenting the application code. Where automatic instrumentation is not enough, developers add spans, attributes and metrics with the SDK, starting from the most critical services.
  5. Fostering adoption. Extending adoption to the whole organization.

I talked about this at containerday 2025 in the talk Incremental Strategies for OpenTelemetry Adoption and on my blog: OpenTelemetry Incremental Adoption Strategies.

Backend and alerting with Prometheus and Alertmanager

As a backend, today my starting point is ClickStack: it can store logs, metrics and traces in a single database (ClickHouse) without having to integrate different products with different query languages.

For alerts I use the classic pairing of Prometheus and Alertmanager: the collector sends metrics to Prometheus, used as a rule engine, and Alertmanager handles grouping, routing and silencing of alerts. Rules and routing are one hundred percent Infrastructure as Code.

Observability for people and AI agents

With an AI agent that knows how to query the data, the graphical interface matters less and less: what you need is well-organized data, in a suitable database, and an agent that has access to it in its harness, for instance through an MCP server. From there, when there is a problem, the agent runs the queries it needs and gets to the cause, often faster than a manual analysis. This way of working requires a well-organized OpenTelemetry infrastructure.

Frequently asked

Does OpenTelemetry replace Datadog, Elastic or Grafana?

Only in part. OpenTelemetry collects and transports the signals, but it is neither a backend nor a console. You send the data to the backend you prefer, commercial or open source, and you can switch backends later without rebuilding the collection infrastructure.

Do we have to start over from scratch?

Not necessarily. I recommend an incremental approach: you start by collecting the telemetry that already exists, from virtual machines and Kubernetes clusters, and only later move to native instrumentation of the applications.

Which backend do you recommend?

It depends on the context, but today my starting point is ClickStack: logs, metrics and traces live in a single database, ClickHouse, and there is no need to integrate three different products. For alerts I use Prometheus and Alertmanager.

Does OpenTelemetry handle alerts too?

No, and that is a design choice: alerts are delegated to the backend. In an OpenTelemetry stack I still prefer Prometheus and Alertmanager, because rules and routing are text files and are managed as code.

Is OpenTelemetry a mature project?

Yes. For logs, metrics and traces it is now mature and complete. It remains a complex project, though, with components at different levels of maturity.

Related reading

Other services

  • Kubernetes ConsultingKubernetes consulting: design, adoption and operation of clusters in the cloud, in the datacenter and at the edge, with a team ready to run them.
  • Cloud ConsultingCloud consulting: architecture and infrastructure on AWS and Google Cloud, hybrid setups, incremental migrations and cloud repatriation. Cloud architect.
  • Platform EngineeringPlatform engineering: building a self-service, declarative and observable platform that people and AI agents can change safely.
  • DevOps ConsultingDevOps consulting: reliable releases, infrastructure as code, cloud costs under control and a platform ready for AI agents.

Let's talk about it

A short email with two lines of context is enough to start.

Email me