x/telemetry/config: completion usefulness counters #66367
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
telemetry
x/telemetry issues
Telemetry-Proposal
Issues proposing new telemetry counters.
Milestone
Counter names
gopls/completion/len:0
gopls/completion/len:<=10
gopls/completion/len:>10
gopls/completion/used:unknown
gopls/completion/used:no
gopls/completion/used:yes
Description
The first set of counters measures the number of suggested completions offered to the user.
The second set of counters measures whether the user accepted any of the suggestions.
Rationale
These counters are intended to measure whether or not users accept proposed completions for Go files.
They count the kinds of completions offered to users, and what the users did with them.
Do the counters carry sensitive user information?
No.
How?
Each completion request from the client results in a set of completions. The counters record the approximate length. The cutoff of 10 is a rough estimate of how many choices the client shows directly to a user.
Then the second set of counters records the user's response evaluated by looking at the changes the client sends back. Sometimes the client sends back a whole file, in which case the user's action is not known. (If this happens a lot it might be possible to sometimes handle this case, but with more work.)
A future set of counters might create a histogram of which suggestion was accepted. The expectation would be that if a suggestion is accepted it would usually be one of the first few.
Proposed Graph Config
New or Update
New
The text was updated successfully, but these errors were encountered: