Actions Usage Metrics is generally available

[natalierjackson]

Actions Usage Metrics is now generally available for all GitHub Enterprise Cloud customers. Actions Usage Metrics enables you to view data about your Actions workflow runs throughout your organization.

You can use this data to identify opportunities to optimize your pipelines and reduce wasted runtime minutes which, when addressed, can lead to faster runs and increased developer productivity.

Actions Usage Metrics breaks down the utilization of workflows, jobs, source repositories, and operating systems for GitHub hosted runners and self-hosted runners. All of this data is available in the UI and can be exported and shared as a .csv file if you wish to integrate your usage data with internal or third party tools.

[geoffreywiseman]

Are there new API endpoints to get this data? I have a GH CLI extension for actions usage and the available information via API is pretty limited at the moment. ;)

[tonyjcamp]

No APIs yes, BUT they're are on our radar. Thank you for voicing your need for them!

[Aviputta1]

@geoffreywiseman may i know which CLI extension are you using to retrieve the actions usage metrics? could you please share the extension documentation. Thanks in Advance.

[geoffreywiseman]

@Aviputta1 The extension is https://github.com/codiform/gh-actions-usage (which effectively replaces https://github.com/geoffreywiseman/gh-actuse). They're pretty limited because the API backing them is pretty limited, which is why I was asking if this new data will have an API I can consume.

[uwehdaub]

It seems that the data is nor consistent.
E.g. when I list e repo on the Repositories tab I get 11 workflows and 582 workflow runs.
When I list the same repo in the Workflows tab I get 15 workflows and a total of 754 WFRs.
But the total minutes match exactly.
This seems to be improvable.

[philip-gai]

👋🏼 Thank you @uwehdaub for the feedback!

The workflow count and workflow runs are different across the tabs because they are aggregated using different dimensions. The workflows tab breaks down the usage by runner type and runtime OS. The repository tab does not. So if Workflow A runs on Repo A and has 2 hosted jobs, job-linux which runs on linux and job-windows which runs on windows, on the repo tab that will count as 1 workflow and 1 run with, say, 100 total minutes. On the workflows tab there will be two different rows, one for Repo A + Workflow A + Hosted + Linux, and one for Repo A + Workflow A + Hosted + Windows , with 1 job and 1 workflow run counted on each row, and say 75 mins and 25 mins respectively. So the total workflows and workflow runs for Repo A on the repo tab will be 1, but the total on the workflows tab if you’re summing up the columns will be 2, but the total minutes will match.

[uwehdaub]

Thank you @philip-gai for the explanation.

I believe these kinds of explanation belongs to the documentation of the feature.
Otherwise more people will stumble on these "inconsistentcies".

[ChrisOwen273]

This would be very useful information to have access to via the API. Would be very interested to hear if this is something planned.

[tonyjcamp]

APIs are on our team's roadmap. Thanks for the feedback!

[TheDevMinerTV]

Now make it available for non-enterprise customers.

[sparker-dg]

Is there a summary report across all enterprise orgs, or are we going to have to assemble that manually. We have 40'ish orgs that are used across our enterprise, and it would be nice to have all this data in one place for back-billing charges to the departments.

[tonyjcamp]

Not today but it's something we're working towards. Based on your goal of assigning billing to departments, you'd still need some manual work because Usage Metrics is showing wall-clock minutes - that is, raw minutes without OS multipliers or large hosted runner premiums. So keep that in mind!

[sparker-dg]

Thanks! I appreciate the tip!

[astendal]

This is a great addition. +1 to previous comments on API support and enterprise-level visibility. Are there plans to break this down further and show invocations of shared workflows and actions? It'd be great to know how often reusable components are being consumed. Additionally, for the runners, it'd be good to know which labels are being invoked so we can distinguish between the different self hosted runners that users are referencing in our enterprise.

[vmasek]

So sad this is only available for Enterprise tier, insights for actions are really missing compared to other cloud runners on the market

[philip-gai]

We have plans in the roadmap to open this up to a broader audience (not just enterprise), so stay tuned!

[Aviputta1]

Hello everyone,

As GitHub Enterprise Cloud customers, we're currently trying to pull usage data for GitHub Actions. I understand that the API currently does not support this functionality.

Our current method involves manually downloading reports from the UI, which is not ideal for our needs. We're looking for a more automated and streamlined approach.

Does anyone know of an alternative way to extract this data, perhaps through a third-party tool such as Splunk or similar? Any guidance or suggestions you could provide would be greatly appreciated.

[philip-gai]

We have plans in the roadmap to support an API for usage data, so stay tuned!

[Ugenx]

Any plans to support Github Enterprise Server?