OpenTelemetry
A vendor-neutral, open-source standard and set of tools for producing traces, metrics and logs and sending them to any backend.
In more detail
OpenTelemetry defines a shared data model, programming interfaces and libraries for many languages, the OTLP protocol and the Collector. Code instrumented with it can switch telemetry backends by changing configuration rather than rewriting handlers.
Examples
tracer.startSpan("checkout", undefined, parentContext)In Node.js the OpenTelemetry SDK relies on AsyncLocalStorage to know which span is current.Related terms
- telemetry — The data a running system sends out about itself, such as logs, metrics and traces.
- observability — How well you can understand what a system is doing, and why, from the data it emits: mainly logs, metrics and traces.
- CNCF — The Cloud Native Computing Foundation: a Linux Foundation organisation that hosts open-source projects such as Kubernetes and OpenTelemetry.
- span — One timed operation within a trace, such as handling a request or running a query, with its start, duration and attributes.
- instrumentation — Code, often a library, that makes an application emit telemetry about its operations.
- OTLP — The OpenTelemetry Protocol: the standard way to send traces, metrics and logs between services, collectors and telemetry backends.
- resource attribute — A label describing what produced telemetry, such as service name, version and environment, attached to every signal.
- distributed tracing — Following one request across every service, queue and database it touches by recording linked spans that share a trace identifier.
- Trace Context — The standard way of passing a trace identifier and parent span identifier from one service to the next, usually in the traceparent header.
- OpenTelemetry Collector — A separate program that receives telemetry from services, processes it and exports it to one or more telemetry backends.
- semantic conventions — OpenTelemetry's agreed names for common attributes, such as http.route and db.system, so every library records the same fact the same way.
- vendor lock-in — Being tied to one supplier because leaving would mean rewriting large parts of your system.
- exporter — A component that sends telemetry out to a backend; in the collector it is the last stage of a pipeline.
Taught in
- What An AI Engineer Does — AI Engineering: LLM Apps, RAG & Agents
- Tracing And Monitoring — AI Engineering: LLM Apps, RAG & Agents
- Capstone: The Tasks Assistant — AI Engineering: LLM Apps, RAG & Agents
- Monitoring A DevOps Environment — Microsoft Azure DevOps Engineer Expert (AZ-400) Exam Prep
- Admin Processes And The Open Source Update — DevOps & Site Reliability Engineering
- OpenTelemetry, Container Publishing and Trimming — Modern .NET Core, C# & Enterprise Microservices
- Distributed Tracing: OpenTelemetry & Traceparent — Production Full-Stack Engineering
- Full-Stack System Verification: Capstone Integration — Production Full-Stack Engineering
- Slow, Or Broken? Metrics, Logs And Traces — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Who Decides What Ships: The CNCF And Its Community — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Architecture Sprint: The Refunds Review — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Script Optimization: next/script & Lazy Third Parties — Next.js 15 & Modern App Router Architecture
- Instrumentation: OpenTelemetry & Performance Spans — Next.js 15 & Modern App Router Architecture
- Routing & Middleware: Path Parsing & Async Context — Node.js Internals & Backend Services
- Observability Versus Monitoring — Full-Stack Observability: Metrics, Tracing & Logging
- OpenTelemetry: The Vendor Neutral Path — Full-Stack Observability: Metrics, Tracing & Logging
- The OpenTelemetry Collector — Full-Stack Observability: Metrics, Tracing & Logging
- Fifteen Traces For Six Bookings: Where Context Was Lost — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Ninety Minutes, No Question Count: Exam Strategy — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Two Names For One Fact: Semantic Conventions And Resources — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Traces From A Script Nobody Touched: Instrumentation Approaches — OpenTelemetry Certified Associate (OTCA) Exam Prep
- A Warning With An Address: Correlating Signals — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fundamentals Sprint: One Declined Card — OpenTelemetry Certified Associate (OTCA) Exam Prep
- A Library That Traces Nothing, Safely: API, SDK And Extension — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fifty Two Spans, Four Requests: The Trace Data Model — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Three Hundred Milliseconds In One Place: Tracing In Code — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Four Bookings Or Two: Instruments And Temporality — OpenTelemetry Certified Associate (OTCA) Exam Prep
- A Histogram That Could Not Answer: Views — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Keep Your Logger: The Logs Bridge And Log Records — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fifty Five Characters: Trace Context And Baggage — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Six Out Of Twelve At One In Four: Samplers — OpenTelemetry Certified Associate (OTCA) Exam Prep
- The Spans Of A Job That Ended Too Soon: SDK Pipelines — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Nine Lines, Five Bugs: Configuring The SDK — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Six Launches, No Code Changes: Language Agents — OpenTelemetry Certified Associate (OTCA) Exam Prep
- API And SDK Sprint: Fourteen Predictions — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Sixty Two New Names: Collector Components And Pipelines — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Validated And Deaf: Checking A Collector Config — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fifty Five In, Fifty Two Out: Transforming Data — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Which Node Was It? Collector Deployment Patterns — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Two Replicas, Half A Trace: Scaling The Collector — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Collector Sprint: Sixteen Predictions — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fifty Four In, Two Out: Debugging A Pipeline — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Failed Twice, Flushed Fine: Error Handling And Schemas — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Maintenance Sprint: Symptoms First — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Forty Four Of Sixty: The Mock And What It Tells You — OpenTelemetry Certified Associate (OTCA) Exam Prep
- The Evening Before: Final Review — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Observability Sprint: One Failed Checkout — Prometheus Certified Associate (PCA) Exam Prep
References
- OpenTelemetry: what is OpenTelemetry
- OpenTelemetry documentation
- .NET observability with OpenTelemetry
- OpenTelemetry: signals
- Next.js 15 docs: OpenTelemetry
Certification courses
- AWS AIP-C01 course and practice exam: AI engineering with LLM apps, RAG and agents
- AZ-400 course and practice exam: Microsoft Azure DevOps Engineer Expert
- KCNA course and practice exam: Kubernetes and Cloud Native Associate
- OTCA course and practice exam: OpenTelemetry Certified Associate
- PCA course and practice exam: Prometheus Certified Associate