Overview | OpenTelemetry
This document provides an overview of the OpenTelemetry project and defines important fundamental terms. Additional term definitions can be found in the glossary. OpenTelemetry Client Architecture At the highest architectural level, OpenTelemetry clients are organized into signals. Each signal provides a specialized form of observability. For example, tracing, metrics, and baggage are three separate signals. Signals share a common subsystem – context propagation – but they function independently from each other.
Overview | OpenTelemetry Ask AI (⌘-K)" class="td-search__input form-control td-search-input" placeholder="Ask AI or search…" aria-label="Ask AI or search…" autocomplete=off> View Markdown View page source Edit this page Create child page Create documentation issue Create project issue On this page Overview This document provides an overview of the OpenTelemetry project and defines important fundamental terms. Additional term definitions can be found in the glossary . OpenTelemetry Client Architecture At the highest architectural level, OpenTelemetry clients are organized into signals .
saved by
related reading
- Tracing APIopentelemetry.io
- Best Practices for Organizing Data - Honeycomb Docsdocs.honeycomb.io
- The Problem with OpenTelemetrycra.mr
- All you need is Wide Events, not “Metrics, Logs and Traces”isburmistrov.substack.com
- OpenTelemetry: A Guide to Observability with Go | Blog | Luca Cavallinlucavall.in
- OpenTelemetry is a CNCF Graduated Projectopentelemetry.io
- Grafana Labs at KubeCon: What is the Future of Observability?grafana.com
- Go Instrumentation Auto SDK | OpenTelemetryopentelemetry.io
- OpenAI Platformplatform.openai.com
- Langfuselangfuse.com
- Grafana OSS | Leading observability tool for visualizations & dashboardsgrafana.com
- What Full-Stack Observability Requires Todaynewrelic.com