Service Level Objective (SLO) and Service Level Indicators (SLI)
Rationale: We’d love it if all our systems responded instantly and worked 100% of the time, but we also know that’s unrealistic. By choosing specific objectives based on what is important to our users, we can aim to keep our users happy, and still be able to prioritize other work as long as we’re meeting those objectives. If the performance starts to dip down toward the threshold, objectively we know it’s time to refocus on short-term reliability work and put other things on hold. And by breaking up our complex production landscape into individual services, each with its own SLOs, we know where to focus that work.
Service Level Indicator
a measurement of a behavior of a system that can be used to monitor the system's function. In the Service Level context ideally expressed as percentage
Service Level Objective
Once we have SLIs we can reason about an objective
Published SLOs
SLO reporting
Quarterly, but offset by one month, i.e. December, January, February.
slide of Tuning Sessions for SLOs
External links
Service Level Objectives at the foundation
Worksheet template

Additional Keywords: Error Budget, RED Method, four golden signals
Last edited on 29 August 2021, at 20:56
Content is available under CC BY-SA 3.0 unless otherwise noted.
Privacy policy
Terms of Use
HomeRandomLog inSettingsDonateAbout WikitechDisclaimers