slo-sli-error-budgets

To define SLIs and set SLO targets, you establish metrics for availability, latency, throughput, and freshness, then use a Nines Table to set realistic targets based on user expectations and dependencies. This skill provides the structural guidance and examples needed to measure and manage service reliability accurately.

An error budget policy dictates deployment velocity based on remaining service reliability margins. You calculate it by subtracting your SLO target from 100%, and this skill provides policy examples for different budget states including healthy, caution, critical, and exhausted to balance development velocity with stability.

Yes, you can use Prometheus queries to track availability and latency SLIs. This skill supports defining these Service Level Indicators by providing specific Prometheus query examples to measure and manage your service reliability metrics effectively.

The best way to configure SLO alerting and review processes is to follow step-by-step implementation guidance for SLO configuration and use provided templates for weekly and quarterly SLO reviews. This ensures continuous measurement and management of service degradation over time.

Error budget management balances development velocity with stability by establishing policies that restrict deployment speed when budgets are low or exhausted. This skill outlines specific budget states to help teams prevent service degradation while maintaining predictable release cycles.

Yes, you need SLOs and SLIs to prevent service degradation for a new API. By defining an availability SLI and setting an SLO target, you establish an error budget policy that dictates deployment speed based on remaining budget, ensuring high availability.