Adding Telemetry #3815
Comments
hyangah
added a commit
to hyangah/delve
that referenced
this issue
Oct 25, 2024
One side effect of it is the go version requirement change. Now it requires go1.22.0 (due to golang.org/x/ modules requirements). For go-delve#3815
hyangah
added a commit
to hyangah/delve
that referenced
this issue
Oct 25, 2024
One side effect of it is the go version requirement change. Now it requires go1.22.0 (due to golang.org/x/ modules requirements). For go-delve#3815
hyangah
added a commit
to hyangah/delve
that referenced
this issue
Oct 25, 2024
Imported golang.org/x/telemetry@a0ccdf0a to avoid go version requirement change. For go-delve#3815
hyangah
added a commit
to hyangah/delve
that referenced
this issue
Oct 28, 2024
Imported golang.org/x/telemetry@9c0d19e to avoid go version requirement change. For go-delve#3815 For golang/go#70056
derekparker
pushed a commit
that referenced
this issue
Oct 29, 2024
Imported golang.org/x/telemetry@9c0d19e to avoid go version requirement change. For #3815 For golang/go#70056
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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
The text was updated successfully, but these errors were encountered: