Remove or update metrics expiring in Firefox 125: fog.validation.validate_early_event before Gecko version gets increased to 125 on 2024-02-19
Categories
(Toolkit :: Telemetry, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
thunderbird_esr115 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox122 | --- | unaffected |
firefox123 | --- | unaffected |
firefox124 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: chutten)
References
Details
(Whiteboard: [metric-expiry-alert])
Attachments
(1 file)
The following metrics will expire in the next Firefox Nightly release: version 125.
fog.validation.validate_early_event
What to do about this:
- If one, some, or all of the metrics are no longer needed, please remove them from their
metrics.yaml
definition file. - If one, some, or all of the metrics are still required, please submit a Data Collection Review and patch to extend their expiry. There is a shorter form for data collection renewal.
If you have any problems, please ask for help on the #glean Matrix room or the #data-help Slack channel.
We'll give you a hand.
Your Friendly Neighbourhood Glean Team
This bug was auto-filed by probe-scraper.
Assignee | ||
Comment 2•1 year ago
|
||
(( Consolidating from bug 1876441: this bug now also needs to deal with the Telemetry Event telemetry.early_event#early_event
. ))
Taking, since I haven't looked at whether the various and several changes (most notably bug 1839426 which hit in 118.0a1 / 20230731215815
) have actually fixed this issue.
Hey, :nalexander, is your browser_launched_to_handle.system_notification
event still looking so different between systems like bug 1837230? I'm asking on the off-chance you already have the answer: I'll happily write the queries if you haven't checked since Fx118.
Comment 3•1 year ago
|
||
(In reply to Chris H-C :chutten from comment #2)
(( Consolidating from bug 1876441: this bug now also needs to deal with the Telemetry Event
telemetry.early_event#early_event
. ))Taking, since I haven't looked at whether the various and several changes (most notably bug 1839426 which hit in
118.0a1 / 20230731215815
) have actually fixed this issue.Hey, :nalexander, is your
browser_launched_to_handle.system_notification
event still looking so different between systems like bug 1837230? I'm asking on the off-chance you already have the answer: I'll happily write the queries if you haven't checked since Fx118.
Looking at the queries from that ticket (slightly updated to not filter by version), I see very similar event counts:
Tag | Glean volume | Legacy volume |
---|---|---|
default-browser-agent |
27,616 | 27,359 |
null#notag |
336 | 319 |
So I have no reason to think the fixes are not working in the wild and that the early event telemetry must be retained.
![]() |
||
Comment 4•1 year ago
|
||
Tracking because toolkit/components/glean/tests/pytest/test_no_expired_metrics.py
checks for this.
Assignee | ||
Comment 5•1 year ago
|
||
Comment 7•1 year ago
|
||
bugherder |
Description
•