You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Big update for lots of recent changes to SG Analytics
## Pull Request approval
You will need to get your PR approved by at least one member of the
Sourcegraph team. For reviews of docs formatting, styles, and component
usage, please tag the docs team via the #docs Slack channel.
Copy file name to clipboardExpand all lines: docs/analytics/index.mdx
+16-8Lines changed: 16 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -75,19 +75,20 @@ Many of the metrics above are also available for Cody only. However, some user d
75
75
| Daily code navigation activity | Count of code navigation operations performed each day |
76
76
| Daily code navigation users | Number of unique users utilizing code navigation features each day |
77
77
| Precise vs. search-based code navigation actions by language | Comparison of precise vs. search-based navigation success rates broken down by programming language |
78
+
| Batch changes usage funnel | Number of times various Batch Changes actions were taken each day: Batch Changes opened, specs created, specs executed, changesets published, and changes merged (from the Sourcegraph UI) |
| Total accepted completions | Count of completions accepted by users during the selected time |
84
-
| Hours saved | The number of hours saved by Cody users, assuming 2 minutes saved per completion |
85
-
| Completions by day | The number of completions suggested by day and by editor. |
86
-
| Completion acceptance rate (CAR) | The percent of completions presented to a user for at least 750ms accepted by day, the editor, day, and month. |
87
-
| Weighted completion acceptance rate (wCAR) | Similar to CAR, but weighted by the number of characters presented in the completion, by the editor, day, and month. This assigns more "weight" to accepted completions that provide more code to the user. |
88
-
| Completion persistence rate | Percent of completions that are retained or mostly retained (67%+ of inserted text) after various time intervals. |
89
-
| Average completion latency (ms) | The average milliseconds of latency before a user is presented with a completion suggestion by an editor. |
90
-
| Acceptance rate by language | CAR and total completion suggestions broken down by editor during the selected time |
84
+
| Total accepted completions & auto-edits| Count of completions and auto-edits accepted by users during the selected time |
85
+
| Hours saved | The number of hours saved by Cody users, assuming 2 minutes saved per completion and auto-edit |
86
+
| Completions and auto-edits by day | The number of completions and auto-edits suggested by day and by editor. |
87
+
| Completion and auto-edit acceptance rate (CAR) | The percent of completions and auto-edits presented to a user for at least 750ms accepted by day, the editor, day, and month. |
88
+
| Weighted completion and auto-edit acceptance rate (wCAR) | Similar to CAR, but weighted by the number of characters presented in the completion and auto-edit, by the editor, day, and month. This assigns more "weight" to accepted completions that provide more code to the user. |
89
+
| Completion persistence rate | Percent of completions that are retained or mostly retained (67%+ of inserted text) after various time intervals. Auto-edits are not included.|
90
+
| Average completion and auto-edit latency (ms) | The average milliseconds of latency before a user is presented with a completion or auto-edit suggestion by an editor. |
91
+
| Acceptance rate by language | CAR and total completion suggestions broken down by editor during the selected time. Auto-edits not included|
91
92
92
93
### Chat and prompt metrics
93
94
@@ -126,6 +127,8 @@ When exporting, you can group the data by:
126
127
- User and day
127
128
- User, day, client, and language
128
129
130
+
And you can select the timeframe for the export using the `startDate` and `endDate` parameters (with `YYYY-MM-DD` values).
131
+
129
132
Each row in the CSV represents a user's activity for a specific combination of these groupings (e.g., a particular day, month, client, and/or language). The CSV includes metrics such as searches, code navigation actions, chat conversations, code completions, and more.
130
133
131
134
#### Important Notes
@@ -155,3 +158,8 @@ Each row in the CSV represents a user's activity for a specific combination of t
155
158
| Total Characters Written by Cody | Inserted code that Cody generates via chat, prompt responses, accepted autocompletions, or suggestions/fixes. Used as the numerator in the "Percentage of Code Written by Cody" ratio. |
156
159
| Total Characters Written | Total new code inserted into the editor (includes both user-generated and Cody-generated characters). Used as the denominator in the "Percentage of Code Written by Cody" ratio. |
157
160
| Percentage of Code Written by Cody | Measures Cody's impact: (Total Characters Written by Cody ÷ Total Characters Written) × 100. [Learn more about this metric.](/analytics/pcw)|
161
+
| Auto-edit suggested events | Number of Cody auto-edit suggestions offered. |
162
+
| Auto-edit accepted events | Number of Cody auto-edit suggestions accepted by the user. |
163
+
| Auto-edit acceptance rate | Ratio of accepted to suggested auto-edits, combined across editors. |
164
+
| Lines changed by chats and commands | Number of lines of code (LOC) changed by chat and command events. |
165
+
| Lines changed by completions and auto-edits | Number of lines of code (LOC) changed by completion and auto-edit events. |
0 commit comments