Service-level agreement

As explained in Cloud Observability in Action

A service level agreement is a contractual commitment by a service provider specifying promised service performance or availability and possible customer remedies for failing to meet it.

A service-level agreement (SLA) is a contractual promise from a service provider to a customer about service performance or availability. It is typically shaped by sales and informed by product and engineering commitments expressed as service-level objectives (SLOs). section 10.1 section 10.1.4

An SLA connects several operational and commercial elements:

• The customer may be external or internal; internal cost attribution can use chargeback or showback. section 10.1
• SLOs define internal reliability goals, while service-level indicators (SLIs) measure whether those goals are met. section 10.1 section 10.4
• Missing an SLA commitment can trigger customer remedies such as refunds, credits, or penalties. section 10.1.4 section 10.2.1

Chat2Much API availability

Engineering estimates that the API can achieve 99.9% availability, while product and sales promise customers 99% over a month. Dashboards and alerts track the underlying SLIs, and customers receive credits if the commitment is missed. section 10.2.1

Figure 10.1 Interaction and dependencies between SLAs, SLOs, and SLIs

Use the relationship diagram to trace how measured SLIs support internal SLOs and ultimately inform contractual SLAs. section 10.1

How Cloud Observability in Action covers it

How deep it goes

Defines contractual scope and remedies, then connects SLAs to SLOs and SLIs without detailing contract drafting.

Examples

Uses a conversational API example with monthly availability, request failures, dashboards, alerts, and customer credits.

What it assumes

Assumes basic service-provider and customer roles, while defining SLOs and SLIs from the distinction between contractual promise and measurement.

What you can do after

Evaluate contractual reliability promises by tracing them to measurable indicators, internal objectives, and explicit customer remedies.

How it connects

Connects service-level agreements with service-level objectives, service-level indicators, availability, reliability, and customer credits.

liveBookmanning.com

Read Cloud Observability in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Think Like a CTOA service-level agreement is a contractually defined agreement that specifies the service commitments, performance levels, and consequences for failing to meet them.
• 

  liveBookmanning.com
  Think Like a Software Engineering ManagerA service-level agreement is a formal agreement that defines expected service performance, availability, and support commitments.

Compare how 3 books explain service-level agreement →

Related concepts

• uptimeconfigures · Uptime is the duration or proportion of a specified period during which a system or service is operational and available to provide its intended function.
• service-level objectivecontrasts with · A service-level objective is a target value or range for a measurable service-level indicator over a specified period.
• mean time to resolutionconfigures · Mean time to resolution is the average elapsed time from identifying or reporting an issue, failure, or incident until it is resolved or affected service is restored.
• serviceconfigures · A service is a capability or activity provided by an entity to meet the needs of users or other components.
• data contractpart of · A data contract is an agreement specifying the structure, meaning, and expectations for data exchanged between producers and consumers.

This explainer was generated by Manning's knowledge graph from the text of Cloud Observability in Action. The section links point to the parts of the book it draws on.