A Site Reliability Engineering (SRE) team manages an e-commerce inventory search API deployed on Cloud Run. The team has established a 30-day rolling Service Level Objective (SLO) of 99.9% availability. They want to receive actionable notifications when an outage threatens to consume their remaining error budget, while avoiding alert fatigue caused by brief, temporary error spikes. Which alerting approach should the team implement in Cloud Monitoring?
- Configure a multi-window burn-rate alert policy based on the rate of error budget consumption.Cevap
- BConfigure a static threshold alert policy that triggers whenever CPU utilization on Cloud Run instances exceeds 85%.
- CConfigure a static metric threshold alert policy that triggers immediately whenever the HTTP 5xx failure rate exceeds 0.1% for 1 minute.
- DConfigure an alert policy based on backend database query latency exceeding a fixed limit of 500 milliseconds.
Cevap
The team should configure a multi-window burn-rate alert policy based on the rate of error budget consumption.
Configuring multi-window burn-rate alerting ensures notifications fire based on the actual speed of error budget consumption. By evaluating both short (e.g., 1 hour) and long (e.g., 6 hours) windows, Cloud Monitoring alerts SREs when a true incident threatens the 30-day SLO budget while suppressing noise from temporary single-minute spikes.
Adım Adım Çözüm
Anahtar Kavram
Error Budget Burn-Rate Alerting
Tahmini Süre:45s