abbreviationSite reliability engineeringpreferred in this glossary

Abbreviation of service level objective

Source: Google SRE book (opens in a new tab)

Target value or range of values for one measured level of a service, such as its average request latency, as a service level indicator measures it.

Source: Google SRE book (opens in a new tab) (adapted)

Adapted: rewords the definition and adds an example of a measured level, request latency. Source: Google SRE book (opens in a new tab)

In plain language

How fast or how reliable a team decides its service should be, written down so it can be measured.

In a sentence

  • The checkout service has an SLO of 99.9 percent of requests completing without error each month.
  • Latency stayed above our SLO for two days, so the team paused feature work to fix it.

Examples written for this glossary

Usage note

Usually written in capitals, and in the plural as SLOs. Each one pairs an indicator with a target: a single limit, or a range between a lower and an upper bound.

Other forms

Not to be confused with

  • Service level agreement

    A contract with users that states consequences, such as a rebate or a penalty, for meeting or missing the targets it contains. A target with no stated consequence is an objective, not an agreement.

    Source: Google SRE book (opens in a new tab)

Why it matters

A written target gives the team a shared test of whether the service is healthy, and tells it when something has gone wrong enough to act.

At Orbyt: p50, p95 and p99 latency, a maximum error rate and an availability percentage are set for each Orbyt Intelligence REST endpoint and measured on every request. They are internal design goals, not a published guarantee; Orbyt publishes no uptime commitment today.

See also

  • Rate limit

    A rate limit caps requests per minute for a user or team, with all team members sharing one bucket: Free 60, Pro 300, Ultra 1,500, counted over a sliding 60-second window.

  • request_id

    A request_id is the identifier Orbyt gives every Intelligence API request: req_ followed by 16 hex characters.

Cite this term.

CC BY 4.0, attribution required.

This term

Orbyt Labs, SLO (Developer Glossary), Nov 6, 2026. https://www.orbytlabs.ai/developers/glossary/slo

The dataset (JSON)

Orbyt Labs Glossaries (Nov 14, 2026), https://www.orbytlabs.ai/glossary#dataset

Last updated .