An enterprise payment processing service hosted on Google Cloud Platform has a defined Service Level Objective (SLO) of availability for its transaction validation API over a -day rolling period. The Service Level Indicator (SLI) evaluates a request as good if it returns an HTTP status code in under .
During a -day window, the service processes a total of requests. Due to a database failover event, requests fail with HTTP internal server errors. Additionally, requests successfully return HTTP but take longer than to complete.
What is the maximum number of additional non-compliant requests the service can sustain before its total error budget for this -day period is completely exhausted?
Cevap: 1600 requests
Cevap
1,600 requests
The total error budget is calculated as of total requests, which equals allowable non-compliant requests. Subtracting the HTTP 500 errors and latency threshold breaches (totaling bad requests) leaves exactly remaining requests in the error budget.
Adım Adım Çözüm
Anahtar Kavram
Calculating Error Budget Consumption using Request-based SLIs