Q: The business asks for an executive dashboard showing whether checkout is healthy. Infrastructure dashboards are too technical. What do you include?
I would build the dashboard around the customer journey, not servers.
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: Business-aligned observability and executive-level SLIs.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
I would build the dashboard around the customer journey, not servers.
- Checkout availability: successful checkout attempts divided by total attempts.
- Checkout latency: P95 or P99 time from cart submit to order confirmation.
- Payment success rate and provider error rate.
- Order creation rate compared with normal baseline.
Remediation & Permanent Safeguards
Top-level signals: Technical panels can exist below the fold, but the first view should answer: "Can customers buy right now, how many are failing, and is this within our reliability target?"
- Revenue-impacting failure count.
- Current SLO status and error budget remaining.
- Active incidents, recent deploys, and rollback status.
- Checkout availability: successful checkout attempts divided by total attempts.
- Checkout latency: P95 or P99 time from cart submit to order confirmation.
- Payment success rate and provider error rate.
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 business asks 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 business asks 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 business asks 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 business asks Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.