Telemetry in Go 1.23 and Beyond
1–10 of 12 posts
Re: Telemetry in Go 1.23 and Beyond
#2[deleted]
Re: Telemetry in Go 1.23 and Beyond
#3Is this telemetry enabled internally at Google? Enabling it internally would be an interesting litmus test of what is required to make it privacy/security compliant.
Re: Telemetry in Go 1.23 and Beyond
#4 go telemetry on
Now, those who need can toggle enable it as needed in a simple fashion.
No global OPT-OUT or OPT-IN, no drama!
Re: Telemetry in Go 1.23 and Beyond
#5Is this telemetry enabled internally at Google? Enabling it internally would be an interesting litmus test of what is required to make it privacy/security compliant.
Most code at Google is built in the cloud (https://bazel.build/remote/rbe), with the compiler running in a sandbox that prohibits network access (https://bazel.build/docs/sandboxing). The language server works similarly. So as a technical matter, this kind of telemetry can't work in that environment.
In principle, the Go telemetry could instead be hooked up to a build-system-specific metric reporting system, and the results from that could then be shared with the Go team. A company that uses a Google-style build system could do that kind of integration work if they wanted to contribute their data. But this doesn't make sense for the scenario where the Go compiler is running on some individual dev's machine; there, you want it to upload the data to Google's servers itself.
Re: Telemetry in Go 1.23 and Beyond
#6Is this telemetry enabled internally at Google? Enabling it internally would be an interesting litmus test of what is required to make it privacy/security compliant.
Most code at Google is built in the cloud ( https://bazel.build/remote/rbe ), with the compiler running in a sandbox that prohibits network access ( https://bazel.build/docs/sandboxing ). The language server works similarly. So as a technical matter, this kind of telemetry can't work in that environment. In principle, the Go telemetry could instead be hooked up to a build-system-specific metric reporting system, and…
> you want it to upload the data to Google's servers itself
Google wants that. Maybe even the Go developers want that. It's not remotely clear that users want that.
Re: Telemetry in Go 1.23 and Beyond
#7Earlier quoted context omitted.
Most code at Google is built in the cloud ( https://bazel.build/remote/rbe ), with the compiler running in a sandbox that prohibits network access ( https://bazel.build/docs/sandboxing ). The language server works similarly. So as a technical matter, this kind of telemetry can't work in that environment. In principle, the Go telemetry could instead be hooked up to a build-system-specific metric reporting system, and…
> you want it to upload the data to Google's servers itself Google wants that. Maybe even the Go developers want that. It's not remotely clear that users want that.
I mean that that's what's required in order for the telemetry to useful enough to be worth doing at all. If you're against telemetry entirely then of course this isn't going to satisfy you, but then there's no point arguing over the details of how it should work.
Re: Telemetry in Go 1.23 and Beyond
#8go telemetry on, to start uploading. go telemetry off to stop logging telemetry data. Isn't this a bit of a weird interface? I didn't check the docs but there must be a way to get to the default setting of log but don't upload.
Re: Telemetry in Go 1.23 and Beyond
#9Is this telemetry enabled internally at Google? Enabling it internally would be an interesting litmus test of what is required to make it privacy/security compliant.
Most code at Google is built in the cloud ( https://bazel.build/remote/rbe ), with the compiler running in a sandbox that prohibits network access ( https://bazel.build/docs/sandboxing ). The language server works similarly. So as a technical matter, this kind of telemetry can't work in that environment. In principle, the Go telemetry could instead be hooked up to a build-system-specific metric reporting system, and…
Also a lot of CI is "start a VM/container, run the build, save the artefacts, wipe everything", whereas the telemetry data is only uploaded every however often; most CI systems wouldn't collect data for long enough to actually send it before getting wiped anyway.
Re: Telemetry in Go 1.23 and Beyond
#10go telemetry on, to start uploading. go telemetry off to stop logging telemetry data. Isn't this a bit of a weird interface? I didn't check the docs but there must be a way to get to the default setting of log but don't upload.
`go telemetry local` will gather local data but not upload it.