Revision as of 18:16, 9 June 2023 edit Petercorless (talk \| contribs) Autopatrolled, Extended confirmed users 7,676 edits Changing from "Google" to "O'Reilly." ← Previous edit		Revision as of 21:51, 9 June 2023 edit undo Stevemcghee (talk \| contribs) 2 edits a first attempt to modernize the article as this term is used a lot now by SREs and this article references a much older use of the term. i can perform a larger edit all at once if that makes more sense. Next edit →
Line 7: There is often confusion in the use of SLAs and SLOs. The SLA is the entire agreement that specifies what service is to be provided, how it is supported, times, locations, costs, performance, and responsibilities of the parties involved. SLOs are specific measurable characteristics of the SLA such as availability, throughput, frequency, response time, or quality. These SLOs together are meant to define the expected service between the provider and the customer and vary depending on the service's urgency, resources, and budget. SLOs provide a quantitative means to define the level of service a customer can expect from a provider.<ref name=":1">{{Cite journal\|last1=Rastegari\|first1=Yousef\|last2=Shams\|first2=Fereidoon\|date=2015-12-29\|title=Optimal Decomposition of Service Level Objectives into Policy Assertions\|journal=The Scientific World Journal\|language=en\|volume=2015\|pages=465074\|doi=10.1155/2015/465074\|issn=2356-6140\|pmc=4709918\|pmid=26962544\|doi-access=free}}</ref> The SLO ~~may~~are beformed ~~composed~~by ofsetting ~~one~~goals orfor ~~more [[quality of service]]~~metrics (~~QoS)~~commonly ~~measurements~~called ([[service level indicator]]s, SLIs) ~~that are combined to produce the SLO achievement value~~. As an example, an availability SLO may ~~depend~~be ondefined ~~multiple~~as ~~components,~~the ~~each~~expected ofmeasured ~~which~~value ~~may~~of ~~have a QoS~~an availability ~~measurement.~~SLI ~~The~~over ~~combination~~a ofprescribed ~~QoS~~duration ~~measures~~(eg: ~~into~~four anweeks). ~~SLO~~The ~~achievement~~availability ~~value~~SLI used will ~~depend~~vary based on the nature and architecture of the service. For example, a simple web service might use the ratio of successful responses served vs the total number of valid requests received. (total_success / total_valid) <ref name="Hidalgo20">{{cite book \|last1=Hidalgo \|first1=Alex \|title=Implementing Service Level Objectives \|date=August 2020 \|publisher=O'Reilly Media, Inc. \|isbn=9781492076766 \|edition=1}}</ref> ==Examples==

Service-level objective: Difference between revisions