define-slo-sli-sla

Establish measurable reliability targets with Service Level Objectives, track them with indicators, and manage error budgets.

Key principle: SLO should be stricter than SLA to provide buffer before customer impact.

Expected: Team understands differences, agreement on which metrics become SLIs, alignment on SLO targets.

Establish Service Level Objectives (SLO), Service Level Indicators (SLI), and Service Level Agreements (SLA) with error budget tracking, burn rate alerts, and automated reporting using Prometheus and tools like Sloth or Pyrra. Use when defining reliability targets for customer-facing services, balancing feature velocity against system reliability through error budgets, migrating from arbitrary uptime goals to data-driven metrics, or implementing Site Reliability Engineering practices. Source: pjt222/development-guides.