Slo Error Budget Burn Rate Alerting

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A DevOps team manages a business-critical microservice running on Google Kubernetes Engine (GKE). The team has defined an availability Service Level Objective (SLO) of 99.9% over a rolling 30-day window.

Currently, the team experiences alert fatigue caused by transient error spikes triggering paging alerts, while simultaneously missing slow, steady budget drain that exhausts the monthly error budget before scheduled reviews.

Which alerting strategy should the team implement in Cloud Monitoring to reliably detect both rapid and slow budget depletion while minimizing false positives?

Configure an alerting policy using the select_slo_budget_fraction time-series selector to trigger an alert when the remaining error budget drops below 50% within a rolling 30-day window.

Configure two separate alerting policies using the select_slo_burn_rate time-series selector: a fast-burn alert with a 1-hour lookback period and a 10x threshold, and a slow-burn alert with a 24-hour lookback period and a 2x threshold.

Configure a single alerting policy using the select_slo_burn_rate selector configured with a 1-hour lookback period and a threshold of 1x baseline.

Configure an alerting policy using the select_slo_compliance time-series selector with a duration of 0 seconds to immediately trigger an incident whenever the compliance ratio drops below 0.999.

Professional Cloud DevOps Engineer

Slo Error Budget Burn Rate Alerting

Related questions