Provide a way to monitor Copilot CLI usage across an org (especially skill usage)

[stonebk]

Describe the feature or problem you'd like to solve

We don't have a way to see how Copilot CLI is being used across our org — especially which skills are being invoked, by whom, and how reliably they run. Without this, we can't tell which skills are delivering value, which are unused, or where users are hitting failures. Claude Code recently shipped monitoring that covers this kind of usage data: https://code.claude.com/docs/en/monitoring-usage. We'd love equivalent visibility from Copilot CLI.

Proposed solution

No strong opinion on the mechanism — we'd defer to the team on the right design. Anything that lets enterprises route usage data into their existing analytics pipeline would work. Claude Code's monitoring docs (linked above) are a useful reference for the kinds of events and fields that have proven valuable.

Example prompts or workflows

• See which skills are used most and least across the org, by team, to decide where to invest in authoring or deprecate unused skills.
• Track success/error rates per skill to catch regressions after a release.
• Attribute Copilot CLI usage to teams for adoption reporting and chargeback.
• Alert on spikes in errors or rate-limit events.

Additional context

Our pipeline is Aria → Azure Data Explorer (Kusto), but other orgs will have their own — so whatever shape the data lands in, having it documented and stable is what matters most.

Reference: https://code.claude.com/docs/en/monitoring-usage

[goldsziggy]

OTEL support did land a couple weeks ago, but you'd need to set the ENV vars on the endpoint devices to start it. Although OTEL may give you a bit much noise with it as well for what your trying to do (correlate usage to teams)

https://code.visualstudio.com/docs/copilot/guides/monitoring-agents#_environment-variables