blob: 13ef0eeb23400d93d301248b08f8fa1558f3bc04 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
|
# Telemetry
## How it works
- We use Segment to record telemetry about user actions
- We record client-side and server-side events
- This data is sent to a Google BigQuery data warehouse
- Data is only updated daily on the free version of Segment
- You can query this data using the Trevor.io tool
## What we track
### Event
Every time a user takes an action that triggers one of the event types below,
we record the VS Code machine ID, time of the event, and the type of event as
well as some additional properties for some of the events.
### Event types
#### ExtensionActivated
Description: Recorded when the VS Code extension is activated.
Location: Client
Properties
- user_id
#### SuggestionAccepted
Description: Recorded when a code fix suggestion is accepted.
Location: Client
Properties
- user_id
#### SuggestionRejected
Description: Recorded when a code fix suggestion is rejected.
Location: Client
Properties
- user_id
#### UniversalPromptQuery
Description: Recorded when a user asks a question to the prompt opened by `cmd+shift+j`
on MacOS or `ctrl+shift+j` on Windows.
Location: Client
Properties
- user_id
- question
#### ExplainCode
Description: Recorded when the `Explain Code` button is clicked.
Location: Client
Properties
- user_id
#### GenerateIdeas
Description: Recorded when the `Generate Ideas` button is clicked.
Location: Client
Properties
- user_id
#### SuggestFix
Description: Recorded when the `Suggest Fix` button is clicked.
Location: Client
Properties
- user_id
#### CreateTest
Description: Recorded when the `Create Test` button is clicked.
Location: Client
Properties
- user_id
#### DebugThisTest
Description: Recorded when the `Debug This Test` button is clicked.
Location: Client
Properties
- user_id
#### GenerateDocstring
Description: Recorded when a user generates a docstring for a function
using `cmd+shift+l` on MacOS or `ctrl+shift+l` on Windows.
Location: Client
Properties
- user_id
#### CodeExplained
Description: Recorded when the server generates a code explanation.
Location: Server
Properties
- user_id
- language
- traceback
- bug_description
- ranges_in_files
- filesystem
- explanation
#### IdeasGenerated
Description: Recorded when the server generates ideas for how to fix.
Location: Server
Properties
- user_id
- language
- traceback
- bug_description
- ranges_in_files
- filesystem
- ideas
#### FixSuggested
Description: Recorded when the server generates a suggested fix.
Location: Server
Properties
- user_id
- language
- traceback
- bug_description
- ranges_in_files
- filesystem
- suggestion
#### TestCreated
Description: Recorded when the server generates a unit test.
Location: Server
Properties
- user_id
- language
- ranges_in_files
- filesystem
- generated_test
#### DocstringGenerated
Description: Recorded when the server generates a docstring.
Location: Server
Properties
- user_id
- language
- ranges_in_files
- filesystem
- docstring
- line_num
### Future Ideas
Client side
- Collect `Enable Highlight` button clicked
- Collect `Disable Highlight` button clicked
- Collect the files that were edited
- Collect the code at a later time to see what it ultimately ended up
- Collect when a debugging session starts
- Collect when a debugging session ends
- Add an ID for bugs based on debugging window (plus, new stack trace)
|
