OpenTelemetry
A vendor-neutral open standard for collecting metrics, logs, and traces from applications. Provides SDKs and a collector that ships telemetry to any observability backend.
What is OpenTelemetry?
A vendor-neutral open standard for collecting metrics, logs, and traces from applications. Provides SDKs and a collector that ships telemetry to any observability backend.
OpenTelemetry is a intermediate-level concept that sits in the Observability & Monitoring area of system design. Engineers reach for it whenever they need to reason about real-world trade-offs in that space — not just for textbook correctness, but because real production systems at companies like Netflix, Amazon, and Google make these decisions every day.
If you want to go deeper than this definition — with diagrams, code, and a quiz to lock it in — work through the "OpenTelemetry" lesson linked below. It walks through the why, the mechanism, the trade-offs, and how the giants actually use it in production.
Learn OpenTelemetry in depth
Full interactive lesson with diagrams, code examples, real-world references, and a quiz.
Open the OpenTelemetry lessonRelated lessons
Lessons that touch on OpenTelemetry as part of a larger topic.
Span IDs
Individual operations within a trace, each span is one unit of work with a start time, duration, and parent
intermediate · observability monitoring
Distributed Context Propagation
Passing trace context, baggage, and metadata across service boundaries, the glue of distributed tracing
intermediate · observability monitoring
Baggage
Custom key-value pairs that travel with the trace context, carrying business data through your distributed system
intermediate · observability monitoring
See also
Related glossary terms you might want to look up next.
Distributed Tracing
Tracking a request as it flows through multiple services in a distributed system. Each service adds its trace, creating a full picture of the request journey.
Metrics
Numerical measurements collected over time that describe system behavior: request rate, error rate, latency percentiles, CPU utilization. Prometheus is the standard collector.
Observability
The ability to understand a system's internal state from its external outputs. Built on three pillars: metrics, logs, and traces.