A global retail company hosts its core checkout microservice on Google Cloud. Executive leadership wants to ensure that technical operational monitoring directly aligns with the business goal of minimizing lost sales revenue during high-volume promotional events. The Site Reliability Engineering (SRE) team needs to define a metric strategy that accurately reflects this business impact. Which approach should the team adopt?
- Define a Service Level Indicator (SLI) measuring the ratio of successful checkout transactions completed under 500 milliseconds, and set a Service Level Objective (SLO) based on the latency threshold where customer purchase drop-off increases.Cevap
- BDefine a Service Level Objective (SLO) as the real-time measurement of backend database query latency, and treat this value as the Service Level Indicator (SLI) target for customer support agreements.
- CSet a Service Level Indicator (SLI) target of maintaining average VM CPU utilization below 80% across backend Compute Engine instance groups during sales events.
- DEstablish a static Service Level Objective (SLO) alert that immediately pages on-call engineers whenever total infrastructure memory usage exceeds 85% for 5 minutes.
Cevap
Define a Service Level Indicator (SLI) measuring the ratio of successful checkout transactions completed under 500 milliseconds, and set a Service Level Objective (SLO) based on the latency threshold where customer purchase drop-off increases.
The correct approach ties the technical metric (checkout latency and success rate) directly to user impact and business performance. In SRE practices, SLIs should measure user-centric experiences (such as request latency on key transactions), and SLO targets should be calibrated against business tolerances, such as conversion rate impact.
Adım Adım Çözüm
Anahtar Kavram
Aligning SLIs and SLOs with User Experience and Business Outcomes