Configurable Time Range
Select a start and end date for the data displaying on the dashboard.
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
Add metrics for the time that jobs spend waiting for containers to become available in order to be able to run.
Alerts and notifications for Insights
As an administrator, operator, or team lead, I would like the ability to configure notifications on Insights to be alerted to unusual behaviors. For example, cited use case was having a lot of junior developers misusing CI resources - they'd like to have alerts or be notified for unusually high-spending jobs, unusually high failure percentages on workflows/jobs/tests, etc.
credits per branch
for a given repository, i'd like to be able to see compute costs when across branches for a given workflow. For example, I want to know how much i've spent on master vs all other branches in the past 30/60/90 days.
Identify timestamp of last data point gathered
Workflow data is empty. Would be great to see the timestamp of the last pull of data to know what's in or out. Not sure how long it will take for data to show in new workflows
test status summary
When using the feature to persist reports, allow better view of the % of tests passing / failing within workflows that export them. This would also be great to have historical charts of within the job view as well (one of the few things that Jenkins does well), but would be useful for the insights feature as well.
Group by branch pattern (regex)
For example, I want to be able to see stats for review branches starting with review/ separately from the main branch or release/ branches.
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.