Trigger Rollback on SLI Breach Instead of SLO Budget Exhaustion
B
Beryl Mandrill
Following the release of the feature enabling automatic CD rollback triggered by SLI/SLO breaches (Long CV), we're suggesting a refinement to the rollback trigger logic.
Currently, rollback is triggered when the SLO budget remaining is exhausted over the evaluation window. The customer recommends enhancing this behavior to react immediately to an SLI breach, rather than waiting for the budget to deplete.
Proposed Enhancement:
Update the SRM module to support rollback triggers based on direct SLI threshold violations, in addition to or instead of relying on SLO budget calculations. This would allow faster response to critical regressions and better alignment with customer expectations around real-time SLI monitoring.
Benefits:
- Faster rollback in response to critical anomalies
- More accurate alignment with customer-defined SLIs
- Greater flexibility in rollback strategy
Log In