Service-level indicator
A service-level indicator is a quantitative measurement of an aspect of a service’s performance, reliability, or behavior.
Cloud Observability in Action
A service level indicator is a quantitative measurement of a service aspect relevant to evaluating a service level objective.
- How it is used
- Measures customer-perceived service performance to evaluate SLOs and inform operational or contractual reliability discussions.
- How deep it goes
- Explains definitions, service-specific measures, organizational relationships, trade-offs, and a worked availability calculation, while deferring deeper SLO terminology.
- Examples
- Uses availability, request errors, latency, completed jobs, throughput, and the Chat2Much API availability calculation.
- What you can do after
- Operate/configure dashboards, alerts, and Prometheus-ecosystem tooling to track SLIs against established SLOs.
Read how Cloud Observability in Action explains service-level indicator →
Effective Platform Engineering
A service-level indicator is a quantitative measurement of a service’s reliability or performance from the perspective of its users.
- How it is used
- Measures user-facing service performance to set expectations, guide reliability work, and connect technical metrics with business priorities.
- How deep it goes
- Defines SLIs and relates them to SLOs and SLAs, then applies them to dashboards, monitoring, and reliability practices.
- Examples
- Uses API response time, latency, throughput, error rates, payment processing, dashboards, and Prometheus data as examples.
- What you can do after
- Apply it via Prometheus and Grafana to define, visualize, monitor, and diagnose reliability objectives.
Read how Effective Platform Engineering explains service-level indicator →
Automating API Delivery
A service level indicator is a quantitative measure of an aspect of a service's health or performance.
- How it is used
- Guides API monitoring and alerting by measuring service health from the customer’s perspective.
- How deep it goes
- Defines quantitative measures and distinguishes SLIs from SLOs and SLAs, while deferring detailed error-budget treatment.
- Examples
- Uses latency, server error rate, throughput, uptime, and a 500-millisecond latency target for 99% of seven-day requests.
- What you can do after
- Apply SLIs to choose customer-relevant monitoring measures and establish the basis for API alerts.
Read how Automating API Delivery explains service-level indicator →
Related concepts
- service-level objectiveconfigured by · A service-level objective is a target value or range for a measurable service-level indicator over a specified period.
- performancekind of · Performance is the measurable effectiveness or operational behavior of a system under specified conditions, assessed through relevant qualities such as task results, speed, responsiveness, throughput, or resource use.
- metrickind of · A metric is a quantitative measure used to characterize or assess a property, condition, behavior, performance, or outcome.
- contractmeasures · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
- meanmeasures · A mean is a measure of central tendency, calculated as the arithmetic average of values or, for a random variable, as the probability-weighted average of its possible values.
- uptimemeasures · Uptime is the duration or proportion of a specified period during which a system or service is operational and available to provide its intended function.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.