DevOps Dictionary

Service Level Objective (SLO) is a specific, measurable reliability or performance target for a service over a defined time window, such as “99.9% of requests succeed over 30 days” or “95% of API calls complete in under 300 ms.” It turns user expectations into an engineering goal by pairing a service level indicator (SLI), the metric that reflects user experience, with a threshold and time period, then tracking actual results against that target. SLOs address the problem of vague “it feels slow” debates by creating a shared definition of acceptable service behavior that can guide alerting, capacity planning, and release decisions.

With a Service Level Objective (SLO), teams can balance feature delivery with reliability using concrete error budgets (the allowable amount of missed target); without it, operations often swings between overreacting to noise and underreacting to real user impact. This gap exists because raw metrics are easy to collect, but only SLOs connect them to outcomes users actually notice.