The vendor-neutral standard for traces, metrics and logs - instrument once, export anywhere. This walkthrough covers the mental model and the configuration you will actually touch.
OpenTelemetry (OTel) is a CNCF standard and SDK set for generating traces, metrics and logs, plus a Collector that receives, processes and exports them to any backend.
The configuration that matters
A Collector pipeline: receive OTLP, batch, export.
receivers:
otlp: { protocols: { grpc: {}, http: {} } }
processors:
batch: {}
exporters:
prometheus: { endpoint: 0.0.0.0:8889 }
otlphttp: { endpoint: https://tempo:4318 }
service:
pipelines:
traces: { receivers: [otlp], processors: [batch], exporters: [otlphttp] }
metrics: { receivers: [otlp], processors: [batch], exporters: [prometheus] }Principles to hold onto
- Send everything to a Collector, then fan out to backends
- Use tail-based sampling for traces to keep the interesting ones
- Propagate context across services with W3C tracecontext
Everyday commands
Auto-instrument a Python app with zero code changes.
pip install opentelemetry-distro opentelemetry-exporter-otlp
opentelemetry-bootstrap -a install
OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317 \
opentelemetry-instrument python app.pyWant senior help putting OpenTelemetry to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.