Question

You operate a customer-facing payments API on Cloud Run and have defined a 99.9% availability SLO over a rolling 30-day window. Your on-call team complains that they receive too many pages for tiny, transient dips that self-resolve, yet they occasionally miss slow-burning degradations until customers report problems. You want an alerting strategy that pages urgently for fast burns and creates lower-priority tickets for slow burns while minimizing false pages. Which approach should you configure in Cloud Monitoring?

Accepted Answer

Configure multiwindow, multi-burn-rate alerting policies on the SLO error budget — a fast-burn policy over short windows for urgent paging and a slow-burn policy over longer windows for ticketing.

Answer

Create a single threshold alert that fires whenever the request error rate exceeds 0.1% for one minute.

Answer

Set an uptime check every 60 seconds against the API and page the on-call team whenever a single check fails.

Answer

Alert only when the remaining 30-day error budget drops below 10%, paging the on-call team immediately when that occurs.