A '''service-level objective''' ('''SLO'''), as per the O'Reilly Site Reliability Engineering book, is a "target value or range of values for a [[service level]] that is measured by aan [[Service Level Indicator|SLI]]."<ref>{{cite web |first1=Chris |last1=Jones |first2=John |last2=Wilkes |first3=Niall |last3=Murphy |editor=Betsy Beyer |title=Site Reliability Engineering: How Google Runs Production Systems |url=https://sre.google/sre-book/service-level-objectives/ |website=Google Site Reliability Engineering |publisher=O'Reilly |access-date=9 June 2023}}</ref> AAn SLO is a key element of a [[Service-level agreement|service-level agreement (SLA)]] between a [[service provider]] and a [[customer]]. SLOs are agreed upon as a means of measuring the performance of the service provider and are outlined as a way of avoiding disputes between the two parties based on misunderstanding.
==Overview==
Line 22:
* Mutually acceptable
While Andrieux et al. define the SLO as "the quality of service aspect of the agreement. Syntactically, it is an assertion over the terms of the agreement as well as such qualities as date and time".<ref name=":0" /> Keller and Ludwig more concisely define aan SLO as "commitment to maintain a particular state of the service in a given period" with respect to the state of the SLA parameters.<ref>Alexander Keller, Heiko Ludwig "The WSLA Framework: Specifying and Monitoring Service Level Agreements for Web Services", Journal of Network and Systems Management, Vol 11, n. 1, March 2003.</ref> Keller and Ludwig go on to state that while service providers will most often be the lead entity in taking on SLOs there is no firm definition as such and any entity can be responsible for aan SLO. Along with this aan SLO can be broken down into a number of different components.
* Obliged - The entity that is required to deliver the SLO.
