Q: After deploying OpenTelemetry instrumentation, traces appear in staging but not production. The application logs show spans are being created. Where do you look first?
If spans are created inside the application but do not reach the backend, the problem is usually between the SDK and the telemetry backend.
Want to master this scenario in a live sandbox? The Linux Foundation's Prometheus Certified Associate (PCA) & Monitoring Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Logs tell you what happened, metrics tell you where to look, and distributed traces pinpoint the exact slow component. The interviewer is testing: OpenTelemetry pipeline debugging, collector/exporter configuration.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
If spans are created inside the application but do not reach the backend, the problem is usually between the SDK and the telemetry backend.
- Collector endpoint: Confirm production points to the correct OpenTelemetry Collector address and protocol (
grpcvshttp/protobuf). - Collector pipelines: Verify the
tracespipeline has a receiver, required processors, and the correct exporter wired together. - Exporter errors: Look at collector logs and metrics such as send failures, queue size, dropped spans, and retry counts.
Remediation & Permanent Safeguards
I would check: The fastest test is to enable collector debug logging or temporarily export to a local logging exporter. That proves whether spans reached the collector before debugging the vendor/backend side.
- Network and auth: Check NetworkPolicy, security groups, proxy settings, API keys, and TLS certificates.
- Sampling: Confirm production is not configured with an accidental 0% sampler.
- Collector endpoint: Confirm production points to the correct OpenTelemetry Collector address and ...
- Collector pipelines: Verify the traces pipeline has a receiver, required processors, and the corr...
- Exporter errors: Look at collector logs and metrics such as send failures, queue size, dropped sp...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Injecting high-cardinality label dimensions (such as user IDs or request UUIDs) into Prometheus metrics when configuring Observability deploying OpenTelemetry High-cardinality label values cause exponential time-series growth, consuming gigabytes of TSDB memory and crashing Prometheus servers.
- Evaluating application performance solely through arithmetic mean or p50 latency while ignoring tail latency (p99) when configuring Observability deploying OpenTelemetry Averages hide catastrophic tail latency outages where 1% of high-value user transactions suffer severe timeouts.
- Failing to inject and extract W3C distributed trace context across message brokers and RPC calls when configuring Observability deploying OpenTelemetry Breaking distributed trace context propagation fragments end-to-end transaction waterfalls into disconnected, un-correlatable trace segments.
- Configuring alert rule evaluation intervals without sufficient duration damping (for: 5m), inducing alert flap when configuring Observability deploying OpenTelemetry Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.