Q: A Prometheus graph shows gaps for a service after pods restart. Does a missing line mean the service was healthy with zero traffic? How do you alert on missing data correctly?
Missing data does not mean zero. It usually means Prometheus did not scrape the target, the metric disappeared, or the pod restarted and the series went stale.
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: "Our SRE team tackled this monitoring and metrics bottleneck to eliminate false-positive alert fatigue. The interviewer is testing: Prometheus staleness, absent metrics, scrape health.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Missing data does not mean zero. It usually means Prometheus did not scrape the target, the metric disappeared, or the pod restarted and the series went stale.
- Zero value: The service exported the metric with value
0. - No series: Prometheus has no current sample for that label set.
Remediation & Permanent Safeguards
I would separate two cases: For scrape health, alert on: For a metric that must always exist, use: or alert when expected targets disappear from service discovery. This prevents treating missing telemetry as healthy behavior.
up{job="checkout"} == 0
- Zero value: The service exported the metric with value 0.
- No series: Prometheus has no current sample for that label set.
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 Prometheus graph 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 Prometheus graph 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 Prometheus graph 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 Prometheus graph Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.