Service Level Objectives (SLOs) are quantitative goals that measure the performance of a service. They help organizations manage customer expectations and ensure service quality.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Theoretical construct: explains a term, principle, or mental model.
Concrete cog in the system that works inside larger relationships.
A Service Level Objective (SLO) is a target value for a service level indicator over a defined time period.
SLOs were introduced in site reliability engineering to manage reliability as a measurable target between product and operations teams. The Google SRE Book describes an SLO as an agreement about the reliability level a service should achieve.
Choose a user-relevant SLI first, then set target, period, and scope, such as 99.9 percent successful requests over 30 days. The gap to perfect service is the error budget. It enables explicit trade-offs between change velocity and reliability; an SLO is neither automatically a contract nor a guarantee.
Sets the desired level of a specific SLI for a population and period.
Expresses tolerated deviation from the SLO and guides risk and change decisions.
Teams use SLOs to align priorities, investment, and operations with user impact.
SLOs turn reliability into an explicit decision language. Good SLOs are attainable, user-focused, and connected to error-budget consequences; the SLI measures reality while the SLO states the target.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.