Demos and production are different sports. This checklist covers what changes when OpenTelemetry has to be reliable, secure and observable under real load.
Security and reliability defaults
- Terminate and authenticate OTLP; don't expose the Collector openly
- Strip PII in processors before export
A production-minded config
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] }Operational best practices
- 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
In production, boring and reproducible beats clever every time.
Want 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.