OpenTelemetry (OTel)
Unified telemetry for cloud-native applications. Traces, metrics, and logs under one vendor-neutral standard.
Sections
- Overview — History, goals, unified model
- Signals — Traces, Metrics, Logs data models
- Traces 101 — TracerProvider, Tracer, Span, SpanContext, patterns
- Metrics 101 — MeterProvider, Meter, Counter, Histogram, Gauge
- Logs 101 — LoggerProvider, Logger, LogRecord, bridge patterns, trace correlation
- SDK & Language Support — API/SDK split, auto-instrumentation, per-language agents
- Collector — Receivers, processors, exporters pipeline
- Context Propagation — W3C Trace Context, Baggage, propagators
- OTLP Protocol — gRPC/HTTP transport, delivery semantics
- Semantic Conventions — Resource and span attribute standards
- Kubernetes Deployment — Agent vs Gateway mode, DaemonSet, resource limits
- OTel Glossary — API vs SDK vs Protocol vs Exporter vs Collector
- Exercise: End-to-End — Go + Python instrumented services to SigNoz
Quick Reference
| Component | Role |
|---|---|
| Signal | Trace, Metric, or Log |
| Span | Single unit of work in a trace |
| Tracer | Creates spans |
| Meter | Creates metrics |
| Collector | Receives, processes, exports telemetry |
| OTLP | Protocol for telemetry transport |