Overview
Direct Answer
A Service Level Indicator (SLI) is a measurable attribute of service performance, such as latency, error rate, or availability, that quantifies one specific dimension of user experience or system behaviour. SLIs form the foundation for defining and tracking whether services meet their intended reliability targets.
How It Works
SLIs are derived from raw metrics collected by observability tools—request response times, failed transactions, uptime periods—and aggregated over defined windows to produce a single percentage or rate. These measurements are then compared against thresholds to determine compliance with service level objectives (SLOs), enabling teams to detect degradation before it impacts end users significantly.
Why It Matters
Organisations rely on SLIs to establish accountability for reliability, justify infrastructure investment, and balance feature velocity against stability concerns. For customer-facing services, poor SLI performance directly correlates with customer churn and revenue loss; for internal systems, it affects productivity and operational costs.
Common Applications
SLIs are used in cloud platforms to monitor uptime and latency, in payment systems to track transaction success rates, and in content delivery networks to measure page load times. DevOps teams use SLIs to trigger automated scaling decisions, whilst incident response teams employ them to prioritise and escalate outages.
Key Considerations
Selecting meaningful SLIs requires understanding actual user impact rather than operational convenience—measuring CPU utilisation, for example, does not necessarily reflect user satisfaction. SLI targets must be ambitious enough to drive quality improvements yet achievable enough to maintain team morale and prevent alert fatigue.
Referenced By1 term mentions Service Level Indicator
Other entries in the wiki whose definition references Service Level Indicator — useful for understanding how this concept connects across DevOps & Infrastructure and adjacent domains.
More in DevOps & Infrastructure
GitOps
Infrastructure as CodeAn operational framework using Git repositories as the single source of truth for declarative infrastructure and applications.
Site Reliability Engineering
Site ReliabilityA discipline applying software engineering principles to infrastructure and operations to create scalable, reliable systems.
Elasticity
CI/CDThe ability of a system to automatically scale resources up or down based on current demand.
Rollback
CI/CDThe process of reverting a system to a previous version or state after a failed deployment or update.
Incident Management
Site ReliabilityThe processes and tools for detecting, responding to, resolving, and learning from service disruptions.
Error Budget
ObservabilityThe maximum amount of time a service can be unavailable within a given period based on its SLO.
Prometheus
ObservabilityAn open-source monitoring and alerting toolkit designed for reliability and scalability in cloud-native environments.
Configuration Management
Infrastructure as CodeThe practice of systematically managing and maintaining the consistency of system configurations.