error-budget-tracker

You can track your SLO error budget and burn rate by querying live observability data from Dynatrace, Prometheus, Datadog, or CloudWatch. The tracker computes current consumption and budget remaining across multiple rolling windows with explicit citations.

SLO error budget burn rate measures how quickly your reliability target is being consumed over rolling windows like 1h, 6h, 24h, 7d, and 30d. It is calculated by comparing live metrics against canonical SRE guidance to flag discrepancies and project exhaustion time.

Yes, you can calculate time-to-exhaustion projections using Datadog or CloudWatch metrics. The tracker compares live data sources against SRE thresholds to project when your error budget will exhaust and returns a recommended action.

You generate a live error budget report for incident reviews through read-only operation, ensuring safe deployments without modifying production data. It returns a structured report including budget remaining, burn rate, and time-to-exhaustion projections with explicit metric citations.

Error budget tracking shows discrepancies between Prometheus and Dynatrace sources due to differences in live metric collection and calculation methods. The tracker explicitly compares these observability data sources and flags any discrepancies found during the SLO budget computation.

Yes, error budget tracking works for capacity planning across 30-day rolling windows. It provides multi-window visibility into burn-rate thresholds and exhaustion time projections, supporting safe deployments and long-term reliability planning.