Missing GitHub Copilot Usage Metrics? Check Telemetry First

Your GitHub Copilot report shows active users, but the feature breakdown is empty. Before interpreting that gap as a drop in use, check whether GitHub received events from the editor. Server activity can establish that someone used Copilot while leaving the report with little detail about what they did.

GitHub’s November 5 update adds separate indicators for client telemetry and editor or extension version requirements. Use them to distinguish a reporting gap from a version problem. Then decide whether you have enough coverage to compare teams or dates.

Start with a completed reporting day

Choose an enterprise or organization report you are authorized to view. GitHub says the usage metrics policy must be enabled, and access depends on the relevant owner, billing or metrics permission. Use a completed day after the new fields became available. GitHub’s usage metrics documentation allows two full UTC days after a day closes for processing. Investigating a partial day can waste time on data that is still arriving.

Keep the same report scope when comparing numbers. An organization’s daily report and an enterprise’s 28-day report answer different questions, even if both contain telemetry counts.

Read the two signals separately

In a user report, client_telemetry_present indicates whether client events arrived for the day. A false value means GitHub saw activity without receiving those editor events. Separately, usage_metrics_requirements reports whether each relevant editor or extension meets the supported version requirements. Missing or null values leave the question open. Preserve that distinction when exporting the data to a spreadsheet.

For example, suppose a developer’s version checks pass but their telemetry flag is false. Review the approved client configuration and network path with the people who own those settings. A version upgrade would address a different signal. If the version is below the minimum, start with the supported update path and check another fully processed day afterward.

Count reporting gaps without double counting

GitHub exposes separate daily totals for users missing client telemetry and users below the version minimum. The same person can appear in both totals. In a fictional report with 12 users in the first group and eight in the second, adding the columns gives 20 flags. It does not tell you how many distinct people were affected. If you need that number and have permission to use the underlying user report, count each affected user once within the chosen scope and period.

Keep daily counts labeled as daily. A single developer may account for several entries across a week. For a team summary, record the date range, scope and missing-data rule alongside every figure.

Separate a dashboard change from a change in behavior

GitHub’s November 6 dashboard update adds Copilot Chat and the VS Code Agents window to feature engagement. GitHub says older reporting periods contain the original feature set and that the additions leave adoption phases unchanged. When a new feature row first appears, mark the reporting change in your chart. Compare only features and periods with compatible definitions.

Activity in an agent window can also involve work on a remote host. For an example of what that workflow looks like, see TechPulse’s guide to previewing a remote app in VS Code. Use the metrics documentation to determine what the report captures.

Write a follow-up someone can act on

Record the report date, the affected scope and the specific signal you observed. Then assign one check: verify a supported editor version, confirm the approved telemetry configuration, or ask your network team to review the client’s connection. Keep individual usage records within approved channels. Recheck after the next complete reporting window and note whether detail returned. If the gap persists, the dated record gives your support team a reproducible starting point.

Prepared with AI assistance using GitHub’s documentation and release notes. The example figures are illustrative. Read the TechPulse editorial policy.