Q: You want to monitor the "availability" of your e-commerce checkout service. How do you calculate it?
Availability shouldn't be measured purely by ping or CPU (host uptime), because the host could be up but the app returning 500 errors.
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: "In an interview, I explain how we designed actionable, symptom-based alerting using the Four Golden Signals. The interviewer is testing: SLI configuration, RED metrics, avoiding ping/uptime as availability.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
Availability shouldn't be measured purely by ping or CPU (host uptime), because the host could be up but the app returning 500 errors. The standard SRE approach uses the RED Method metrics, specifically Error Rate. I would calculate availability as a ratio of successful requests to total requests over a window (e.g., 30 days). Availability % = (Total Requests - HTTP 5xx Errors) / Total Requests * 100 This provides the Service Level Indicator (SLI). To make it actionable, I would set a Service Level Objective (SLO), such as 99.9%, and alert if the Error Budget burn rate exceeds an acceptable threshold.
- Immediate Triage: Availability shouldn't be measured purely by ping or CPU (host uptime), because the host could
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
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 want monitor 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 want monitor 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 want monitor 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 want monitor Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.