Service Level Objective (SLO)

I. Formal Definition

A target value or range for a service-level indicator, expressed as a percentage over a rolling window, that represents the reliability commitment between the operating team and the consumers of the service. The SLO is not the same as the service-level agreement: the SLO is internal and operational, while the agreement is external and contractual. The federation expects SLOs to be tighter than any external agreement and to be the input to error-budget accounting under UFMS-001:2.4.

II. Etymology

Formalised alongside SLI in the Google Site Reliability Engineering literature of 2016; the underlying concept of operational targets predates the formalisation by decades.

III. Federation Usage

Federation members must publish SLOs, the rolling window, and the historical attainment series. SLOs without an attainment series older than ninety days are reported as undocumented under MEV-Annex:3.2.

IV. Related Terms

• sli
• error-budget
• incident-postmortem
• metrics

V. Authoritative Citations

• UFMS-001:2.4UFMS Article II - Objective Standard
• MEV-Annex:3.2MEV Annex III - Attainment Series

VI. Citation in BibTeX

@misc{ifo4_glossary_slo,
  title        = {{Service Level Objective (SLO)}},
  author       = {{IFO4 Federation Editorial Board}},
  howpublished = {{IFO4 Federation Glossary, slug \texttt{slo}}},
  year         = {2026},
  url          = {https://ifo4.org/glossary/slo},
  note         = {Category: DevOps; key: ServiceLevelObjectiveSLO}
}

VII. Challenge This Definition

Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.