Skip to content

Commit 24a7d1d

Browse files
28 days to 100 days (#57241)
Co-authored-by: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com>
1 parent d737eb7 commit 24a7d1d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/copilot/tutorials/roll-out-at-scale/measure-adoption/analyze-usage-over-time.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ You can use the [AUTOTITLE](/rest/copilot/copilot-metrics) to see trends in how
2525

2626
The API includes:
2727

28-
* Data for the last 28 days
28+
* Data for the last 100 days
2929
* Numbers of active users and engaged users
3030
* Breakdowns by language and IDE
3131
* The option to view metrics for an enterprise, organization, or team
@@ -125,7 +125,7 @@ In your terminal, you should see output with a JSON array like the following.
125125

126126
## 3. Store the data
127127

128-
To analyze trends over longer than 28 days, you will need to:
128+
To analyze trends over longer than 100 days, you will need to:
129129

130130
* Call the API daily, using a cron job or scheduled {% data variables.product.prodname_actions %} workflow.
131131
* Store data locally or with a database service such as MySQL.
@@ -208,7 +208,7 @@ If you run the script again tomorrow, it should only save data for one new day t
208208
209209
## 4. Analyze trends
210210
211-
You can work with the data from the API to identify trends over the last 28 days or, if you've stored data from previous API calls, over a longer period.
211+
You can work with the data from the API to identify trends over the last 100 days or, if you've stored data from previous API calls, over a longer period.
212212
213213
### Example
214214

0 commit comments

Comments
 (0)