Revisando dados de atividade dos usuários para o Copilot na organização

Analise os dados de uso do GitHub Copilot na sua organização para tomar decisões informadas sobre a atribuição de estações.

Quem pode usar esse recurso?

Organization owners

Organizations with a subscription to Copilot Business

Neste artigo

Reviewing user activity data for Copilot

  1. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.

  2. Next to the organization, click Settings.

  3. In the "Code, planning, and automation" section of the sidebar, click Copilot, and then click Access.

  4. At the top of the page, under "GitHub Copilot," you can see an overview of your organization's GitHub Copilot usage. You can see the number seats assigned through your Copilot Business subscription, and the estimated monthly cost.

    Screenshot of the GitHub Copilot usage overview.

  5. For more detailed information, next to "Access management," click Get report.

    GitHub generates a report for you, which you can download as a CSV file.

  6. Alternatively, under "Access management," you can use the Sort options to sort the list of users by when they last used GitHub Copilot.

Using the API to retrieve assignment information

You can use GitHub's REST API to get details about the assignment of GitHub Copilot seats in your organization. See "Get Copilot seat information and settings for an organization," "List all Copilot seat assignments for an organization," and "Get Copilot seat assignment details for a user."

Understanding the last_activity_at calculation

Note

This data is in public preview and subject to change.

To align the last_activity_at data point with actual usage, the system returns the timestamp of a user's most recent interaction with Copilot functionality. These interactions are:

  • Receiving a code suggestion in an IDE
  • Chatting with Copilot Chat in an IDE
  • Interacting with Copilot on a mobile device
  • Interacting with Copilot Chat for CLI

The last_activity_at date is consistent across the CSV generated via Get Report in Copilot Access settings as well as through GitHub's REST API. The events which are tracked come from both client, and server-side telemetry. This allows the timestamp to be durable in the event that network conditions would impact client-telemetry.

Troubleshooting last_activity_at data

Processing new telemetry events and updating a user's last_activity_at date can take up to 24 hours. Users must have telemetry enabled in their IDE for their usage to be reflected in last_activity_at.

If you believe a user's last_activity_at date should be more recent than shown in the CSV or API report, please wait 24 hours and check again. If their recent Copilot usage is still not reflected in their last_activity_at date, have the user check that telemetry is enabled in their IDE settings.

For more information about enabling telemetry in various IDEs, see:

Further reading