Skip to content

Commit bc36811

Browse files
[EDI] Move content about last_activity_at Copilot property to Reference article (#56615)
Co-authored-by: hubwriter <[email protected]>
1 parent 8970450 commit bc36811

File tree

4 files changed

+51
-23
lines changed

4 files changed

+51
-23
lines changed

content/copilot/how-tos/administer/organizations/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization.md

Lines changed: 3 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -41,31 +41,11 @@ redirect_from:
4141

4242
You can use {% data variables.product.prodname_dotcom %}'s REST API to get details about the assignment of {% data variables.product.prodname_copilot %} seats in your organization. See [Get Copilot seat information and settings for an organization](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#get-copilot-seat-information-and-settings-for-an-organization), [List all Copilot seat assignments for an organization](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#list-all-copilot-seat-assignments-for-an-organization), and [Get Copilot seat assignment details for a user](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#get-copilot-seat-assignment-details-for-a-user).
4343

44-
## Understanding the `last_activity_at` calculation
44+
## Troubleshooting `last_activity_at` data
4545

46-
> [!NOTE] This data is in {% data variables.release-phases.public_preview %} and subject to change.
46+
If you believe a user's `last_activity_at` date should be more recent than shown in the CSV or API report, 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.
4747

48-
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:
49-
50-
* Receiving a code suggestion in an IDE
51-
* Chatting with Copilot Chat in an IDE
52-
{%- ifversion ghec %}
53-
* Creating or updating a knowledge base
54-
* Creating a pull request summary
55-
* Interacting with Copilot Chat in GitHub
56-
{%- endif %}
57-
* Interacting with Copilot on a mobile device
58-
* Interacting with Copilot Chat for CLI
59-
60-
The `last_activity_at` date is consistent across the CSV generated via `Get Report` in Copilot Access settings as well as through {% data variables.product.prodname_dotcom %}'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.
61-
62-
The retention period for `last_activity_at` data is 90 days. After 90 days of no new activity, a user's `last_activity_at` value is set to `nil`. The data retention period cannot be modified. For more information, see [Updating retention period for `last_activity_at` values on the Copilot user management API to 90 days](https://github.blog/changelog/2025-01-17-updating-retention-period-for-last_activity_at-values-on-the-user-management-api-public-preview-to-90-days/) on {% data variables.product.prodname_blog %}.
63-
64-
### Troubleshooting `last_activity_at` data
65-
66-
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`.
67-
68-
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.
48+
For more information about this property, see [AUTOTITLE](/copilot/reference/metrics-data#last_activity_at).
6949

7050
## Further reading
7151

content/copilot/reference/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,5 +11,6 @@ children:
1111
- /ai-models
1212
- /proxy-server-and-firewall-settings-for-copilot
1313
- /copilot-extensions
14+
- /metrics-data
1415
---
1516

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
title: Metrics data properties for GitHub Copilot
3+
shortTitle: Metrics data
4+
intro: 'See how GitHub calculates properties from APIs and reports.'
5+
versions:
6+
feature: copilot
7+
topics:
8+
- Copilot
9+
allowTitleToDifferFromFilename: true
10+
---
11+
12+
## `last_activity_at`
13+
14+
> [!NOTE] This data is in {% data variables.release-phases.public_preview %} and subject to change.
15+
16+
The timestamp of a user's most recent interaction with {% data variables.product.prodname_copilot_short %} functionality.
17+
18+
### Surfaces
19+
20+
This property is consistent across the following surfaces:
21+
22+
* The CSV report downloaded from the "Access management" page (see [AUTOTITLE](/copilot/how-tos/administer/organizations/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization))
23+
* The [AUTOTITLE](/rest/copilot/copilot-user-management)
24+
25+
### Calculation
26+
27+
The following interactions count as activity:
28+
29+
* Receiving a code suggestion in an IDE
30+
* Chatting with Copilot Chat in an IDE
31+
* Creating or updating a knowledge base
32+
* Creating a pull request summary
33+
* Interacting with Copilot Chat in GitHub
34+
* Interacting with Copilot on a mobile device
35+
* Interacting with Copilot Chat for CLI
36+
37+
The tracked events come from both client- and server-side telemetry, ensuring the timestamp is durable if network conditions affect client-side telemetry.
38+
39+
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`.
40+
41+
### Retention period
42+
43+
* The retention period for `last_activity_at` data is 90 days. This cannot be modified.
44+
* After 90 days of no new activity, a user's `last_activity_at` value is set to `nil`.
45+
46+
For more information, see [Updating retention period for `last_activity_at` values on the Copilot user management API to 90 days](https://github.blog/changelog/2025-01-17-updating-retention-period-for-last_activity_at-values-on-the-user-management-api-public-preview-to-90-days/) on {% data variables.product.prodname_blog %}.

content/copilot/tutorials/rolling-out-github-copilot-at-scale/assigning-licenses/reminding-inactive-users.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,5 +159,6 @@ jobs:
159159
160160
## Further reading
161161
162+
* [AUTOTITLE](/copilot/reference/metrics-data#last_activity_at)
162163
* [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/driving-copilot-adoption-in-your-company)
163164
* [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/analyzing-usage-over-time-with-the-copilot-metrics-api)

0 commit comments

Comments
 (0)