Error Categorization
next fiscal quarter
M
Maroon Rhinoceros
I would like for failed, expired and errored pipelines to be categorized into Application vs Platform failures. Application failures would be any situation where the application team controls the solution. Platform failures are any situation where the application team has to engage another group to resolve. It would be helpful to also have a sub-category for failure. This will help us analyze failure trends for enhancements, performance, and to detect production incidents early. Examples:
* Application Issues: Pipeline configuration problems, Failed tests, Expired approval, Scripting errors, Container startup failure, Policy Failure
* Platform Issues: Connection Failures (e.g. artifactory, bitbucket), Delegate disconnected/restarted, Pipeline failure on any account-scope template step, POD startup failures, POD eviction
Log In
Prasad Satam
next fiscal quarter
I'm thrilled to inform you that your idea has been carefully reviewed and evaluated by our product team. We are excited to announce that it has been given top priority and is now officially in our development pipeline for the next Fiscal Quarter!
We will keep you updated on the progress and let you know as soon as it is available.
Should you have any questions, suggestions, or thoughts you'd like to share, please feel free to add more to this feature request.
Rohan Gupta
under review
Looking into this one, we are reviewing feasability of this request.