Question

Your team runs a payment API on Cloud Run and has defined a Cloud Monitoring service with a 99.9% availability SLO over a rolling 28-day window. On-call engineers complain they receive too many alerts for tiny, temporary error blips that never threaten the monthly target, yet they still want to be paged quickly when a real outage is rapidly consuming the error budget. Which Cloud Monitoring feature should you configure to meet both needs?

Accepted Answer

An SLO burn-rate alerting policy that pages only when the error budget is being consumed faster than a defined threshold over a lookback window

Answer

A metric-threshold alerting policy that fires whenever the request error rate exceeds 0.1% for 1 minute

Answer

An uptime check against the Cloud Run URL with a notification channel to the on-call PagerDuty service

Answer

A log-based metric counting 5xx responses with an alert on every non-zero value