Add metrics for the time that jobs spend waiting for containers to become available in order to be able to run.
Aggregate Workflow Metrics / Insights across branches
Currently I can only view insights against a single branch. I would like to be able to remove brach as a filter altogether in order to see the aggregate metrics across all runs of a workflow.
Show tags in Insights
Currently, it is not possible to show insights for tags. It would be greate if we could show all tag insights since those are the ones we use most often
Insights: Option to filter on multiple branches
Currently, both the Insights UI and API, can only retrieve statistics filtered on a single branch. However, it is very limited if the exact same workflows are run on multiple branches. It would be great to have filter that can filter on multiple branches and all branches,
Insights by Job
We use a monorepo in which insights by Job (historical, graphs) is just as essential as insights by Workflow and Repo.
Email insights metrics and credit consumption once per month
We'd love to see the main insights page in email form sent once a week so I can keep an eye on high level metrics and understand my credit consumption.
Add display name in junit test insghts
In junit test insights, instead of showing the method name, show the display name.
More historical insights data
Users can select time windows between last 24 hours and last 90 days. Would like to see more historical data like last 1 year, all time, and so on.
Workflow success vs. failure rate calculation
How is the workflow success vs. failure rate calculated? I'm looking at the Workflow Success Rate chart and failures seem to be overstated? We make use of cancelled workflow jobs a lot in our deployment pipelines -- for these charts to be useful, we need a way to either exclude cancelled workflows or treat them as success not failure.
Report the Accelerate Metrics
The book Accelerate describes four core metrics to measure the performance of your team: Development Frequency, Lead time for changes, Time to restore service, and Change failure rate. Having these metrics in CircleCI would be brilliant, as I see CircleCI as having all these metrics ready to calculate. This article nicely describes the concept: https://www.gocd.org/2018/10/30/measure-continuous-delivery-process/ Here's the link to the book: https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations-ebook/dp/B07B9F83WM