Service Level Objectives (SLOs) are central to's monitoring capabilities, serving as the main indicators of the health and effectiveness of service operations which, in turn, inform the overall health of broader services and user journeys within your application.
SLOs establish well-defined goals for application performance, aiding teams in:
  • delivering a reliable user experience
  • balancing between new feature roll-outs and system reliability
  • and facilitating communication among different stakeholders

Key Concepts


Service Level Objectives (SLOs) are internal targets set for an app's reliability metrics like availability or response time.

Service Level

The service level indicates the actual success rate of a given operation. You can compare a service level against an SLO's target to understand whether the SLO is being fulfilled or not.

Error Budgets

This is the allowable limit of unreliability for a system within a set time frame - think of it as a cushion for tolerable failures and a resource for development.
Teams use the notion of "remaining error budget" to communicate how close an SLO is from being broken. The closest your service level is from your SLO target, the least remaining error budget you have.

Burn Rate

The burn metric indicates how quickly you're using your error budget. High burn rate indicate you'll exhaust your budget quicker, which can suggest there are problems occurring.