SLO Burn Rate Early Warning
warningFastAPI services with defined SLOs (success rate and latency objectives) can detect reliability degradation before total failure by monitoring error budget burn rate. A burn rate exceeding 1.0 indicates the service is consuming its error budget faster than sustainable.
Track error budget burn rate derived from request success rates and latency percentiles against defined SLO targets. Alert when burn rate exceeds 1.0, indicating the service will exhaust its error budget before the SLO measurement window completes.
Configure Prometheus alerting rules for SLO burn rate violations. When burn rate exceeds 1.0, investigate recent deployment changes, traffic pattern shifts, or dependency degradation. Use the autometrics-generated SLO labels to identify which function groups are burning budget fastest and prioritize remediation.