Glossary · Monitoring

SLI (Service Level Indicator)

An SLI is a measured number that describes one aspect of service quality, such as the share of requests that succeed or finish under a latency target.

Updated October 6, 2026

A Service Level Indicator (SLI) is a quantitative measurement of how well a service is behaving from the user's point of view. It is usually expressed as a ratio of good events to total events, for example successful requests divided by all requests.

Why it matters

SLIs are the raw material for reliability targets. An SLO is a goal set on top of an SLI, and an SLA is a contract that usually builds on the SLO. Without a well-chosen SLI, a target such as "99.9%" has no agreed meaning. Good SLIs reflect what users feel: whether pages load, whether checkouts complete, whether answers arrive quickly. CPU load or memory use rarely qualify because users never see them directly.

Example

For an online shop you might define two SLIs over a rolling 30 days:

availability SLI = checks returning HTTP 200 / total checks
latency SLI      = requests answered in under 500 ms / total requests

If 4,320 of 4,330 checks passed, the availability SLI is about 99.77%.

Common mistakes

  • Measuring only from inside your own network. A site can look healthy internally while users cannot reach it.
  • Using averages for latency. A few very slow requests disappear in the mean, so ratios against a threshold or percentiles are safer.
  • Tracking dozens of SLIs. Start with one to three per user-facing journey.

Get notified when this term updates

Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.

Keep reading

Glossary · MonitoringBlack-Box MonitoringBlack-box monitoring tests a system from the outside, the way a user would, to detect symptoms like errors and slowness without inspecting internals.Glossary · MonitoringBulkhead PatternThe bulkhead pattern isolates resources into separate pools so a failure or overload in one part of a system cannot exhaust capacity for the rest.Glossary · MonitoringFalse Negative (Monitoring)In monitoring, a false negative is a missed failure: the check reports healthy while real users are affected, so no alert is sent.Guide · MonitoringAlert Fatigue and On-Call Basics for Small TeamsSet severity levels, escalation paths, alert thresholds and runbooks so a small team gets paged for real problems only and still sleeps through the night.8 min readGuide · MonitoringCron Job Heartbeat Monitoring to Catch Silent Failures EarlyLearn how heartbeat monitoring catches silent cron failures, with copy-ready examples for crontab, systemd, GitHub Actions, Docker, WP-Cron, Laravel and more.9 min readGuide · MonitoringHow Often Should You Monitor a Website? Choosing Check IntervalsPick the right uptime check interval for each part of your site. See how interval, retries and alert delay combine into real detection time, and what to avoid.8 min read

This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.