Change Failure Rate (CFR) – Expanded Failure Identification Criteria when using CI/CD systems
C
Closed Minnow
CFR today tracks failed pipeline executions vs successful executions. This underrepresents real production failures, which may include:
- Rollbacks
- Hotfix deployments
- Deployments linked to incidents
The goal is to expand failure identification criteria for Change Failure Rate beyond pipeline failure status.
We propose SEI to allow Admins to define production failure using configurable criteria such as:
- Rollback deployment detected
- Deployment tagged with incident ID
- Incident created within X hours of deployment
- Custom tag/label indicating failed release
- Linked Jira incident ticket
Support logical rules:
- AND/OR combinations
- Time-window association between deployment and incident
Expected Outcome
More accurate DORA-aligned CFR.
Ability to align measurement with organizational definition of production failure.
Better auditability of what qualifies as a failed change.
Log In