x/telemetry/config: collect gopls/telemetryprompt/accepted

[findleyr]

Summary

From gopls, we ask a select fraction of users to enable telemetry via an LSP prompt (a showMessageRequest dialog). Starting in gopls@v0.16.1, we record a gopls/telemetryprompt/accepted counter when users accept the prompt.

By collecting this counter, we can estimate the fraction of new telemetry participants that are coming from the prompt, which will help us evaluate the efficacy of the prompt itself.

Of course, we cannot know how many users decline the prompt.

Proposed Config Change

https://go.dev/cl/603936

[gabyhelp]

Related Issues and Documentation

• x/tools/gopls: add a prompt to ask users if they want to enable Go telemetry #62576 (closed)
• x/tools/gopls: add telemetry counters that will help with the v0.17.0 release #68240 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[findleyr]

It occurred to me that because we have a conservative cutoff, we won't ever upload the counter file for the day that telemetry is enabled: we only upload counter files that do not overlap with any period of time when telemetry uploading was not enabled.

Therefore, I think gopls should record at every startup whether the prompt was accepted. Theoretically, we could also record other prompt outcomes: some users may decline the prompt but enable telemetry via other means.

Putting this in the gopls@v0.16.2 milestone to address the collection issue.

[cagedmantis]

cc @golang/telemetry

[gopherbot]

Change https://go.dev/cl/603936 mentions this issue: internal/chartconfig: add collection for gopls/telemetryprompt/accepted

[gopherbot]

Change https://go.dev/cl/607758 mentions this issue: gopls: increment the telemetryprompt acceptance counter for each session

[gopherbot]

Change https://go.dev/cl/609135 mentions this issue: [gopls-release-branch.0.16] gopls: increment the telemetryprompt acceptance counter for each session