Examkin

Soru

Zorluk: OrtaDefining and Managing SLOs, SLIs, and Error Budgets

An e-commerce company operates a real-time recommendation engine microservice on Google Cloud Run. The Site Reliability Engineering (SRE) team defines a Service Level Objective (SLO) requiring 99.9% of valid requests to return successful HTTP responses over a rolling 30-day window. During flash sales, transient traffic spikes occasionally consume substantial portions of the monthly error budget within a few hours before static alerts trigger, leading to exhaustion of the budget without timely intervention. Which monitoring and alerting configuration should the team implement in Cloud Monitoring to detect fast budget consumption before the error budget is fully depleted?

  1. Configure multi-window, multi-burn-rate alerts in Cloud Monitoring that measure short-term (e.g., 1-hour) and long-term (e.g., 6-hour) burn rates against a defined percentage of error budget consumption.Cevap
  2. B
    Set up a static threshold metric alert in Cloud Monitoring that triggers an incident whenever CPU utilization on the Cloud Run instances exceeds 85% for more than 5 minutes.
  3. C
    Create a static threshold alert on the 5xx HTTP error count metric to trigger when the error count exceeds 50 errors within a 5-minute rolling window.
  4. D
    Redefine the Service Level Indicator (SLI) metric target from 99.9% to 99.0% whenever traffic spikes occur to prevent premature alerting.

Cevap

Configure multi-window, multi-burn-rate alerts in Cloud Monitoring that calculate consumption rates over multiple time windows.
Implementing multi-window, multi-burn-rate alerting in Cloud Monitoring allows SRE teams to measure the rate at which the error budget is being consumed over both short (e.g., 1 hour) and longer (e.g., 6 hours) windows. This ensures rapid detection of critical outages while preventing alert fatigue caused by minor, temporary spikes.

Adım Adım Çözüm

1
Identify the reliability monitoring requirement.
The requirement is to detect severe, rapid error budget consumption (burn rate) dynamically during high-traffic periods before the 30-day budget is depleted.
Static threshold alerts fail to adapt to varying request volumes and do not reflect budget consumption speed.
2
Evaluate SRE best practices for Cloud Monitoring SLO alerting.
Multi-window, multi-burn-rate alerting uses both short-term (fast reaction) and long-term (high precision) burn-rate thresholds against the total allowable budget.
This strategy alerts page-worthy events promptly when the error budget is burning fast enough to threaten the SLO window.

Anahtar Kavram

Error Budget Burn Rate Alerting
Bu soruyu puanla

Konular

Defining and Managing SLOs, SLIs, and Error Budgets

Bu konudan daha fazla soru