Q: What is an absence alert, and when would you use one?
An absence alert fires when expected telemetry stops arriving.
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: Missing signal detection.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
An absence alert fires when expected telemetry stops arriving.
- A cron job should publish
backup_success_totalevery night, but no sample appears. - A payment service should always have some traffic during business hours, but request metrics disappear.
- A log shipper stops sending heartbeat logs.
Remediation & Permanent Safeguards
Examples: This is different from alerting on a metric value. You are alerting that the signal itself is missing. Absence alerts are useful for batch jobs, telemetry pipelines, and critical services where "no data" might mean monitoring is broken or the job never ran.
- A cron job should publish backup_success_total every night, but no sample appears.
- A payment service should always have some traffic during business hours, but request metrics disa...
- A log shipper stops sending heartbeat logs.
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 absence alert 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 absence alert 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 absence alert 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 absence alert Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.