Service-level objective: Difference between revisions

Content deleted Content added
Kumouri (talk | contribs)
m Overview: Change "throughout" to "throughput" in the list of measurable characteristics as that seems the most likely thing meant
Citation bot (talk | contribs)
m Alter: pages. Removed URL that duplicated unique identifier. | You can use this bot yourself. Report bugs here.| Activated by User:Headbomb
Line 4:
 
==Overview==
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|last=Rastegari|first=Yousef|last2=Shams|first2=Fereidoon|date=2015-12-29|title=Optimal Decomposition of Service Level Objectives into Policy Assertions|url=http://www.hindawi.com/journals/tswj/2015/465074/|journal=The Scientific World Journal|language=en|volume=2015|pages=1–9465074|doi=10.1155/2015/465074|issn=2356-6140|pmc=4709918|pmid=26962544}}</ref>
 
The SLO may be composed of one or more [[quality of service]] (QoS) measurements ([[service level indicator]]s, SLIs) that are combined to produce the SLO achievement value. As an example, an availability SLO may depend on multiple components, each of which may have a QoS availability measurement. The combination of QoS measures into an SLO achievement value will depend on the nature and architecture of the service.