In February I posted a series of blog posts defining Transparent Telemetry, and we had a lively discussion on #58409. In the original posts, the design was opt-out. Based on that discussion as well as private discussions with long-time contributors and users, I revised the design to be opt-in.

I propose that we add opt-in transparent telemetry to the Go toolchain as described in those posts, specifically “The Design of Transparent Telemetry.” Transparent Telemetry has the following key properties:

• The decisions about what metrics to collect are made in an open, public process.
• The collection configuration is automatically generated from the actively tracked metrics: no data is collected that isn’t needed for the metrics.
• The collection configuration is served using a tamper-evident transparent log, making it very difficult to serve different collection configurations to different systems.
• The collection configuration is a cacheable, proxied Go module, so any privacy-enhancing local Go proxy already in use for ordinary modules will automatically be used for collection configuration.
• Uploaded reports only include total event counts over a full week, not any kind of time-ordered event trace.
• Uploaded reports do not include user IDs, ma