Service-level objective

As explained in Cloud Observability in Action

A service level objective is a target value or range for a service reliability or performance measure over a specified time period.

A service level objective (SLO) is a target value or range for a service reliability or performance measure over a defined period. Teams compare service level indicators (SLIs), such as error rate, with the SLO to determine whether the goal was met. section 2.4.4 section 10.1.3

SLOs are goals for the service team rather than direct customer contracts. Product owners define them with engineering and sales, and may use them to inform service level agreements (SLAs). section 10.1 section 10.1.3

Use SLOs to connect reliability measurement with operational and commercial decisions:

• Set availability, error-rate, or other reliability goals over an explicit time window. section 2.4.4 section 10.1.3
• Track the goal with defined SLIs, dashboards, alerts, and periodic reporting. section 10.2.1 section 10.4
• Balance reliability against delivery velocity: stricter targets require more effort, and dependencies can limit achievable reliability. section 10.1.3
• Use results to support customer commitments, credits, compliance reporting, and more accurate early-warning alerts. section 10.0 section 10.4

Chat2Much API availability

A product owner proposes 99% monthly availability for a conversational chatbot API. Engineering estimates that 99.9% is achievable with the current team and technology, defines metrics A, B, and C as SLIs, and reports monthly performance. Sales can then base an SLA and possible customer credits on the agreed SLO. A load test with 1,000,000 requests and 6,942 failures can be rounded to 7,000 tolerated failures, supporting a realistic 99% availability commitment. section 10.2.1

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

Use the dependency diagram to distinguish SLAs, SLOs, and SLIs and see how customer, business, product, and engineering roles connect. section 10.1

How Cloud Observability in Action covers it

How deep it goes

Explains definitions, roles, trade-offs, dependencies, implementation workflow, and tooling, while deferring detailed SLO mathematics.

Examples

Uses monthly API availability, request failures, load-test counts, dashboards, alerts, and customer credits as concrete examples.

What it assumes

Assumes basic metrics and observability knowledge while distinguishing SLIs, SLOs, and SLAs explicitly.

What you can do after

Apply it via Prometheus ecosystem tools by defining SLIs, comparing them with goals, and reporting or alerting on results.

How it connects

Connects SLOs with service level indicators, service level agreements, metrics, observability, alerting, Prometheus, and OpenSLO.

liveBookmanning.com

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

Also explained in

• 

  liveBookmanning.com
  Effective Platform EngineeringA service-level objective is a target value or range for a service-level indicator that defines an intended level of service performance or reliability.
• 

  liveBookmanning.com
  Google Anthos in ActionA service-level objective is a target value or range for a service-level indicator that expresses an expected level of service performance.

Compare how 3 books explain service-level objective →

Related concepts

• service-level indicatorconfigures · A service-level indicator is a quantitative measurement of an aspect of a service’s performance, reliability, or behavior.
• service-level agreementcontrasts with · A service-level agreement is a formal agreement or commitment that specifies measurable service expectations, responsibilities, and related terms between parties.

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.