liveBook · Manning

Service-level indicator

As explained in Microservices Patterns, Second Edition

A service level indicator is a quantitative measurement of an API's or service's real-world behavior.

A service-level indicator (SLI) is a quantitative measure of an API’s real-world behavior, such as latency, error rate, or uptime. An SLO sets a target for an SLI; an SLA makes one or more SLOs contractual. section 8.1.3

Teams instrument APIs to collect the metrics that drive SLIs. Observability infrastructure collects metrics, logs, and traces and compares service behavior with objectives, helping teams detect reliability issues. section 8.1.3

Table 8.2 Some example SLOs for a service, each of which is a well-defined performance target
SLO Type Description Example Target

Availability

Ensures that the API is reachable and functioning for consumers.

At least 99.9% of requests succeed over a rolling 30-day period.

Latency

Measures how quickly the API responds to requests.

95% of requests complete within 200 milliseconds.

End-to-End Processing (Asynchronous)

Measures how long it takes for published events to be processed by downstream consumers.

99% of events are processed successfully within one minute.

Data Freshness

Ensures that derived views, caches, or replicas reflect recent updates.

Replicated data is updated within 60 seconds of a change.

Examples show targets for availability, latency, asynchronous processing, and data freshness. section 8.1.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines SLIs and relates them to SLOs, SLAs, and observability without detailing metric instrumentation.
Examples
Illustrates availability, latency, asynchronous processing, and data-freshness targets.
What you can do after
Evaluate API behavior by monitoring latency, error rate, or uptime against SLO targets.
How it connects
Connects SLIs to service-level objectives, service-level agreements, and observability.

Also explained in

Compare how 4 books explain service-level indicator →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.