monitoring

To define SLIs and SLOs for a production API, you use standard formulas for availability, latency percentiles, error rates, and throughput, then configure rolling windows and targets to measure service reliability.

Error budget burn rate alerting works by tracking specific burn rate thresholds against rolling-window SLOs, triggering recommended actions and alert severities when error budgets reach green, yellow, red, or exhausted states.

The difference between USE and RED dashboard patterns is that USE focuses on resource utilization, saturation, and errors, while RED tracks rate, errors, and duration for service monitoring.

To create a 30-day SLO with actionable alerts, you configure rolling-window SLOs for your service, define burn rate thresholds for green, yellow, red, and exhausted error budget states, and apply alert severity principles to reduce downtime.

Yes, you can use these SLO templates for capacity planning and forecasting by applying the provided capacity planning template, which helps forecast scaling needs and prioritize reliability work based on tracked error budgets.

You should run an error budget review for your services monthly to evaluate error budget states, assess burn rate thresholds, and prioritize reliability work to reduce unplanned downtime.