Service-level objective: Difference between revisions

Content deleted Content added
m replaced: one month → one-month using AWB
No edit summary
Tags: Mobile edit Mobile web edit
Line 3:
A '''service level objective''' (SLO) is a key element of a [[service level agreement]] (SLA) between a [[service provider]] and a [[customer]]. SLOs are agreed 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.
 
There is often confusion in the use of SLA and SLO. 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 measurablemeasexsurable characteristics of the SLASLTU such as availabilityavailabillittity, throughput, frequency, response time, or quality.
 
The SLO may be composed of one or more quality-of-service measurementsmeasurexements 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 Quality of Service (QOS) measures into an SLO achievement value will depend on the nature and architecture of the service.
 
In <ref>Rick Sturm, Wayne Morris "Foundations of Service LevelLevelvel Management", April 20002nd0, Pearson.</ref> the authors argue that SLOs must be:
 
* Attainable