⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Observability & Monitoring Interview Questions Scenario 73 of 116 in Observability & Monitoring
Junior / Associate DevOps [L1] Observability OpenTelemetry & Tracing Core Fundamentals [L1]
🎯 Target Role / Context: Observability Scenario #72 (L1) · Procedure #1: Clear Deadlock

Q: What is an absence alert, and when would you use one?

An absence alert fires when expected telemetry stops arriving.

#Observability #L1 #Monitoring #Prometheus #SRE
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
⚡ Recommended Practice Lab

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."

1️⃣

Initial Diagnostics & Root Cause Analysis

An absence alert fires when expected telemetry stops arriving.

  • 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 disappear.
  • A log shipper stops sending heartbeat logs.
2️⃣

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.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: A cron job should publish backup_success_total every night, but no sample appears.."
⚡ 60-Second Elevator Pitch Talking Points
  • 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.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
Advertisement
Want more Observability & Monitoring scenarios?
Explore our complete collection of scenario-based Observability & Monitoring interview runbooks.
Browse All Observability & Monitoring Questions →