Closed
Bug 2018330
Opened 9 months ago
Closed 8 months ago
Create a Legacy Telemetry migration aid (a "worst offenders" spreadsheet with links to re:dash queries and code involving the probe)
Categories
(Toolkit :: Telemetry, task, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
People
(Reporter: chutten, Assigned: chutten)
References
Details
To scale our migration efforts, we'll need to provide helpful tools for people to use independently to migrate their collections away from Legacy Telemetry. We imagine that core to this effort will be a spreadsheet of Legacy Telemetry probes, ordered by size, and providing convenience links to find them in code and in analysis.
This bug's about creating such a spreadsheet.
| Assignee | ||
Comment 1•9 months ago
•
|
||
We need a map of probe name <-> metric name. Luckily, the probe info service has that information for us. Unluckily, there's no way to get gsheets to import it like the way we can for data in the data platform with BQ connectors.
But this works:
- Download https://probeinfo.telemetry.mozilla.org/glean/gecko/metrics and https://probeinfo.telemetry.mozilla.org/glean/firefox-desktop/metrics
- Process the resulting JSON into CSV of
metric name, probe namelike so:
cat gecko_metrics_20260220.json firefox-desktop_metrics_20260220.json | jq --raw-output 'to_entries | .[] | select(.value.history[-1].telemetry_mirror and .value["in-source"]) | [.key, (.value.history[-1].telemetry_mirror | ltrimstr("h#") | ascii_downcase), .value.type] | @csv' | sort > ~/Downloads/gifftmap.csv - Import the resulting csv into a sheet
(( Why do we need the Glean metric type? Mostly to distinguish the table the resulting probes might be found in. ))
| Assignee | ||
Comment 2•8 months ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•