Change failure rate is great to know about, but how do we make it specifically actionable? Ideas?
#187
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As of now, I can tell that out of 50 deployments, 5 had issues after them, then CFR turns out to be 10%.
What are some general ideas that we can implement regarding making this data more actionable?
Can we leverage notifications (maybe emails?), or correlations, etc.?
Beta Was this translation helpful? Give feedback.
All reactions