Project-level metrics for the Insights API
under review
A
Anna Calinawan
Right now the Insights API endpoints provide metrics at the branch-level. This means aggregating data for a given project requires iterating through all of the branches.It would be helpful to have project-level metrics to get a clearer bird's eye view of usage.
CCI-I-1487
Merged in a post:
Show number of builds per-project in Insights
Nick Presta
When viewing the Insights data for a project, it would be very useful to know the number of builds (where a workflow with several steps is still counted as a single build) for a given project. This allows us to figure out how active a project is, and the time savings/loss by slowing down or speeding up our builds.
CCI-I-306
Merged in a post:
Consolidated view of all projects (similar to the Insights feature)
M
Mark Hopson
I would like the Insights page to show an aggregated view of stats from all my projects
I think this is useful because as a Sys Admin, i have a high level over view on usage and failures happening in everyone's build pipeline.
CCI-I-465
Merged in a post:
Project-level Insights
C
Cyril Lakech
In general, it is more useful to investigate the credit consumption at a project or organization level than at a branch level.The Insights API returns information on a per-branch basis, but right now there's no easy way to get a list of all of the branches from the CircleCI API. This makes it difficult to get a project-level overview of credit consumption.It would be great if those API could provide a way to aggregate all branch credits cost in the same call.
CCI-I-1508
Merged in a post:
Show insights by project and not only by the branch
A
Ana Vale
Lately, the "Insights" show us the frequency that a test breaks in a branch in our repo. But this information is not sufficient for us, so it would be great if there was a way that Insights showed what tests were broken by project and not only by branches.
CCI-I-234
E
Erin Stanfill
+1 this.I really want to see failed tests insights at the project level. Flaky tests in PRs delay delivery and having insight into which tests need attention would allow me to advocate for spending time fixing specific tests.
K
Kunal Jain
Thank you so much for your feedback. Internally, we have discussed to provide this data at different levels eg. organization or project.
Would any of you be interested in doing a formal user interview with us? It is 45 min video call to capture feedback around metrics that you are expecting out of a CI tool. If you are interested, please fill this survey.
Thank you so much!
A
Adam
+1 - it would definitely be more useful to see insights rolled up to the project level rather than being forgotten about at the individual branch level.
T
Tom King
+1, the default slicing of builds by branch leads to mostly useless results, since some builds include migrations etc and we want a more consistent trend graph of how long our tests are taking.
S
Steve Munday
+1 this.
Half of our runs are on master, and half are on PR status checks. The PR status checks are not shown in Insights because they are always on different branches. Those are the ones more likely to fail, and therefore more interesting to analyze.