OpenTelemetry
What is it?
OpenTelemetry is an open standard and toolkit for collecting logs, metrics, and traces from software in a consistent, vendor-neutral way.
Explain like I'm 5
Why was it created?
Each monitoring vendor had its own way to collect data, causing lock-in. OpenTelemetry was created as a shared standard so you instrument once and stay portable.
Where is it used?
- Instrumenting apps for observability
- Collecting traces, metrics, logs
- Avoiding vendor lock-in
- Standardizing telemetry across services
Why should developers care?
It has become the common standard for observability data, so engineers increasingly use it to instrument services.
How does it work?
You add OpenTelemetry libraries to your code to produce telemetry in a standard format. A collector receives and processes it, then exports it to any compatible backend (dashboards, tracing tools), so switching tools doesn't mean re-instrumenting.
Real-world example
A company instruments its services with OpenTelemetry once, then sends the data to its chosen observability platform — and can switch platforms later without changing code.
Common use cases
- Vendor-neutral instrumentation
- Unified traces/metrics/logs
- Portability between tools
- Standardized observability
Advantages
- Open, vendor-neutral standard
- Instrument once, export anywhere
- Covers all three signals
- Broad industry support
Disadvantages
- Setup complexity
- Still maturing in places
- Overhead if over-instrumented
- Learning curve
When should you use it?
When you want standardized, portable observability across services and tools.
When should you avoid it?
For a tiny project where a simpler built-in monitoring solution is enough.
Alternatives
Related terms
Interview questions
Beginner
- What does OpenTelemetry do?
- What three signals does it cover?
Intermediate
- What is the OpenTelemetry collector?
- How does it avoid vendor lock-in?
Senior
- How do you control telemetry overhead and sampling?
- Why standardize instrumentation across services?
Common misconceptions
- "OpenTelemetry is a monitoring dashboard" — it collects and exports data; you still use a backend to visualize it.
- "It locks you into one vendor" — its whole purpose is the opposite: portability.
Fun facts
- It's often abbreviated OTel.
- It unifies the three observability pillars — logs, metrics, and traces — under one standard.
Timeline
- 2019 — OpenTelemetry forms by merging two earlier observability projects
Learning resources
Quick summary
OpenTelemetry is a vendor-neutral standard and toolkit for collecting logs, metrics, and traces, so you instrument once and export anywhere.
Cheat sheet
- Open standard for telemetry
- Logs + metrics + traces
- Instrument once, export anywhere
- Avoids vendor lock-in