Question

Your SRE team manages a customer-facing payments API running on GKE. Leadership has approved a 99.9% availability SLO measured over a rolling 28-day window. The team wants an automated, low-noise way to be alerted while there is still enough error budget remaining to react, rather than only after the SLO is already breached. Which approach in Google Cloud Observability best meets this requirement?

Accepted Answer

Configure a Cloud Monitoring SLO with multi-window, multi-burn-rate alerting policies that fire on fast and slow error-budget consumption.

Answer

Create a single threshold alert that fires whenever the 28-day availability metric drops below 99.9%.

Answer

Set up an uptime check that pings the API every minute and pages the on-call engineer on any single failed probe.

Answer

Build a Cloud Monitoring dashboard showing request success rate and have engineers visually review it during business hours.