DevOpsInterviewPrep logo
← Observability, SLOs & Reliability / 11
hard★ EssentialNewUberRazorpayPhonePe

Write the PromQL behind our availability SLO and tell me where these queries usually go wrong.

Anyone can divide bad requests by total. This answer shows the aggregation mistakes that quietly corrupt SLO dashboards, the rate-versus-increase traps that make budgets lie, and when subqueries cost too much.

Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.

Anyone can divide bad requests by total. This answer shows the aggregation mistakes that quietly corrupt SLO dashboards, the rate-versus-increase traps that make budgets lie, and when subqueries cost too much.

an account raises the per-topic limit · no card
UP NEXT ON YOUR JOURNEY
Next in this trackOne Grafana serves three hundred teams and half the dashboards are abandoned. How do you organise it?Next in this trackFollow one log line from the application into Elasticsearch and onto the Kibana screen. Where does this path break at scale?Next in this trackPick a trace-sampling strategy for our checkout service and defend it.
DISCUSSION · 0

Nothing here yet. Say how you would answer it.