Copilot metrics is now generally available 🚀

[ebndev]

GitHub Copilot usage metrics is now generally available, giving you a single place to see how your teams adopt and use Copilot. This way you can track trends, make informed decisions about rollout, and build reports that fit your organization.

Since the public preview at Universe 2025, Copilot usage metrics has expanded with organization-level visibility, fine-grained access controls, data residency support, and more. Here's what you can expect now that it's generally available.

What’s included

Dashboards

• Copilot usage dashboard provides clear, actionable insights into how your teams are using GitHub Copilot. The dashboard provides visibility into code completion activity, IDE usage, model and language breakdown, and more.
• Code generation dashboard gives a directional measure of Copilot’s output by quantifying the lines it suggested, added, or deleted across completions, chat, and agent features.
• Enterprise and organization-level granularity allows enterprise and organization owners to track adoption and usage trends for their teams without relying solely on enterprise-wide aggregates.

APIs

• Enterprise-level: Get a bird's eye view of all Copilot usage across your entire enterprise for aggregate analysis on user engagement, Copilot usage, pull request throughput, and more.
• Organization-level: Organizations can programmatically access their own Copilot usage to understand how teams are engaging with Copilot, spot trends, and assess enablement efforts.
• User-level: Analyze individual Copilot usage for a specific day to support enablement and identify where teams may need training or better documentation.

Check out our API documentation to learn more.

Access and availability

• For access, navigate to your enterprise account → AI Controls → Copilot → Metrics → Copilot usage metrics. You should then see the dashboard under Insights → Copilot usage or Code generation. Please also ensure you are either an Enterprise Administrator, Billing Manager, or have the proper fine-grained permissions to have access to Copilot metrics.
• Fine-grained access controls let you share visibility with the right people using custom enterprise roles, such as View enterprise Copilot metrics, without requiring full admin access.
• Added support for GitHub Enterprise Cloud with data residency so enterprises with residency requirements can access Copilot usage dashboards and API reporting.

What's next

Today's release delivers the data foundation for understanding Copilot adoption across your organization. The next question many leaders are asking is "is it working?" We're building toward that answer—connecting usage patterns to engineering outcomes so you can move from tracking adoption to measuring impact. We'll share more as these capabilities become available.

To get started, visit Copilot usage metrics documentation.

🌟Leave a comment!

Join the discussion and leave feedback in the comments below!

[jsoref]

Using a percentage when you have a divide by zero case results in garbage:

February 21 and onward, there were 0 users which means the denominator was 0, but the graph shows a line going to 0 as if there were users and they somehow used an undefined model.

[jsoref]

Model usage per day and Language usage per day are confusingly similar and yet incompatible graphs.

• Paired with Copilot metrics is now generally available 🚀 #188142 (comment)

How is it that I have language usage on a day when I have no model usage? What does that mean??

The answer is in the very fine print:

Model usage per day

Daily breakdown of models used in requests across all chat modes, excluding code completions

Language usage per day

Daily breakdown of language usage in requests across all chat modes and code completions

If the data sets are sufficiently incompatible, then there should be a horizontal rule:

---

To separate them and clearly indicate that they can't be reasoned over together.

[jsoref]

0.0% should not be shown in pie or donut charts:

[jsoref]

Colors should not be reused in adjacent graphs unless they mean the same thing:

On the left, "properties" is Orange, on the right, "properties" is everything.

Also, "Most frequently used model in each language for user-initiated chat requests" seems to imply there would be a column for each thing from the left, but "ignore" and "Other languages" are definitely not present in columns on the right.

[jsoref]

Language usage per day keys are confusing

Other languages is painted in the key as a solid orange line, but in the graph, it's dashed:

• See also Copilot metrics is now generally available 🚀 #188142 (comment)

[jsoref]

Model usage per language uses squares in the top key and then circles in the hover key

Why bother? Why not use circles in both places?

[jsoref]

popups show circles instead of the right icon

This picture is from "Language usage per day"...
The popup for the points shows simple circles for each item, but the items have shapes (orange circle, cyan diamond, green square, purple upwards pointing triangle, blue downwards pointing triangle):

[jsoref]

Painting 0% items on a stacked graph is confusing

This appears to be some very confused stacked percentage graph.

It'd be much simpler to not plot things that are zero percent than to have them intersperse their 0% coloration along the lines where they don't travel.

• Note that Gemini is a purple diamond and OpenAI is a blue square as flagged in Copilot metrics is now generally available 🚀 #188142 (comment)

[jsoref]

Graphs for the same timescale inconsistently show dates

• Requests per chat mode shows dates for each day
• Code completions shows dates for every second day

There's no need to be inconsistent like this.

It isn't that the dates wouldn't fit for horizontal text, as Model usage per day manages it w/o issue.