Adding Telemetry

[derekparker]

The Delve team together with the Go team have proposed that Go telemetry metrics collection be added to Delve[0]. The gathering of this data would happen in accordance with the upstream guidelines for telemetry data collection[1]. Just as with telemetry in the Go toolchain, data collection will happen locally and exporting of this data can be controlled via go telemetry.

We are proposing to add metrics around the following data points:

• Usage by GOOS/GOARCH, Go/Delve versions
• Usage by Delve subcommands, DAP mode, RPC versions, flags
• Performance metrics (latency)
• Crash monitoring
• Internal errors
• Missing features in the expression language
• Potential UI improvements for IDE’s

This information will be useful to the Delve maintainers to help guide development efforts, fix unreported bugs, and continue to ensure the overall user experience and functionality is in alignment with what our users expect.

This issue will track the ongoing work and serve as a place for community feedback.

—
[0]: golang/go#68384
[1]: https://go.dev/doc/telemetry#background