The front page of https://telemetry.go.dev is still largely a placeholder. We should improve it prior to the Go 1.23 release, which includes support for opt-in telemetry. At that time, people will want to know more about telemetry, as well as view telemetry data that has been collected thus far.
There is a lot of room for improvement, since the page is currently just a bunch of links. We discussed this in our team meeting, and had a few ideas for how it could be improved. More ideas are welcome.
Minimum requirements - The content of the Overview section must remain prominently displayed. - We should filter the links to recent data, or paginate them (but the full set of data must remain accessible, for example at an /all url). - We should show a summary of recent data. For example, we could choose a selection of charts, and generate them based on data merged from the last week of reports. This may require some pre-processing on the worker.
Other ideas - Show timelapse data. For example, a chart of go/gopls version usage by week would be interesting. - ~Add a download form that allows specifying a date range, and downloading a zip file with all telemetry data in that date range.~ (Let's stick to static content, per Russ's comment below). - Show a chart of # uploads by day/week, to provide info about opt-in rate - Incorporate some way to view stack counter data. For example, we'd be interested in showing recent gopls crashes.
CC @golang/telemetry @ansaba @h9jiang
Comment From: rsc
It'd be nice to stick to static content, so I'd avoid the download form. People can script downloads easily enough. The others all sound good. I agree with the minimum requirements, and let's focus on doing those before anything else. Thanks!
Comment From: prattmic
It would be nice if this page prominently displayed how to opt in/out of telemetry collection, or at least linked directly to https://go.dev/doc/telemetry#config. Right now it is a bit circuitous to figure out: first decide to click the "learn more" link to https://go.dev/doc/telemetry, and then decide to go to the "Configuration" section.
Comment From: ansaba
We should show a summary of recent data. For example, we could choose a selection of charts, and generate them based on data merged from the last week of reports. This may require some pre-processing on the worker. will require merging of data and extra work.
It the work seems like a Stretch goal, an easier way would be Filter on date range and provide Next pagination on individual date page.
Comment From: findleyr
It the work seems like a Stretch goal, an easier way would be Filter on date range and provide Next pagination on individual date page.
@ansaba just to make sure I understand the suggestion: you mean rather than merge the last week of charts, just show the most recent day's chart, with a pagination to go back/forward in time. Agree we can do that if we don't have time to merge data. Longer term it would be nice to see the prior week's data, since the upload happens once a week and so the past week of data represents active users.
Comment From: gopherbot
Change https://go.dev/cl/598695 mentions this issue: _content/doc: improve visibility of configuration in telemetry documentation
Comment From: gopherbot
Change https://go.dev/cl/599275 mentions this issue: telemetrygodev: restyle, and add charts to the root page
Comment From: gopherbot
Change https://go.dev/cl/599595 mentions this issue: telemetrygodev: switch backgrounds of chart content
Comment From: gopherbot
Change https://go.dev/cl/602996 mentions this issue: godev/cmd/telemetrygodev: show aggregate charts on the root page
Comment From: gopherbot
Change https://go.dev/cl/603835 mentions this issue: godev/cmd/telemetrygodev: further style / content tweaks for charts
Comment From: findleyr
We've deployed the CLs above to https://telemetry.go.dev. There is of course more that we could do, but we'll probably stop here. The home page is styled more like a subpage of go.dev, and has some aggregate charts for the last week. The chart viewer itself has a dynamic floating menu that makes it easier to click around to different charts (which will be more important as we add more collection).
For true exploration of the data, we'd be better served by ingesting telemetry data into a database or perhaps cloud monitoring, where it can be dynamically queried and charted. That is a project for another day.