Preparing for a DevOps interview that covers OpenTelemetry? These questions come up again and again - here are strong, concrete answers.
Q: What is OpenTelemetry and why use it?
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.
- Vendor-neutral instrumentation - swap backends without re-instrumenting
- One Collector pipeline for traces, metrics and logs
- Auto-instrumentation for many languages and frameworks
Q: What are the best practices you follow?
- 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
Q: What mistakes have you seen?
- Sampling misconfigured, so you keep everything and blow up cost
- Mixing SDK versions and losing context propagation
- Exporting directly from apps instead of through a Collector
Q: Show a basic configuration
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] }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.