# Agent Service Level Objectives and Error Budgets
Status: public
Confidence: medium (0.725) (verified)
Last verified: 2026-06-02
Generation: ai_structured


## TL;DR

SLOs and error budgets help agents judge whether a service problem is a reliability risk, a release blocker, or tolerable operational noise.

## Core Explanation

Agents that triage incidents or release changes need service reliability context. An SLI is the measurement, an SLO is the target, and an error budget is the amount of unreliability left before the service breaches its objective. That context changes what remediation is appropriate.

For agent decisions, SLO data should be used as a constraint. A low error budget should make the agent prefer safer rollbacks, reduced blast radius, or human approval. A healthy budget can support controlled experiments, but not unsupported claims about user impact.

## Source-Mapped Facts

- Google Cloud documentation describes service-level objectives as targets that define acceptable service reliability. ([source](https://docs.cloud.google.com/stackdriver/docs/solutions/slo-monitoring))
- Prometheus alerting documentation describes alerting rules as a way to define alert conditions based on expression results. ([source](https://prometheus.io/docs/practices/alerting/))
- Atlassian documentation distinguishes SLIs as measurements, SLOs as targets, and SLAs as agreements. ([source](https://www.atlassian.com/incident-management/kpis/sla-vs-slo-vs-sli))

## Further Reading

- [Google Cloud SLO Monitoring](https://docs.cloud.google.com/stackdriver/docs/solutions/slo-monitoring)
- [Prometheus Alerting Rules](https://prometheus.io/docs/practices/alerting/)
- [Atlassian SLA vs SLO vs SLI](https://www.atlassian.com/incident-management/kpis/sla-vs-slo-vs-sli)