Remove or update metrics expiring in Firefox 123: urlbar.quick_suggest_contextual_opt_in before Gecko version gets increased to 123 on 2023-12-18
Categories
(Firefox :: Address Bar, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox120 | --- | unaffected |
| firefox121 | --- | unaffected |
| firefox122 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: dao)
References
Details
(Whiteboard: [metric-expiry-alert][sng])
Attachments
(2 files)
|
343 bytes,
text/plain
|
travis_
:
data-review+
|
Details |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
The following metrics will expire in the next Firefox Nightly release: version 123.
urlbar.quick_suggest_contextual_opt_in
What to do about this:
- If one, some, or all of the metrics are no longer needed, please remove them from their
metrics.yamldefinition 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.
Comment 1•2 years ago
|
||
Tracking because at least toolkit/components/glean/tests/pytest/test_no_expired_metrics.py checks for this.
Comment 2•2 years ago
|
||
The bug is marked as tracked for firefox122 (nightly). However, the bug still isn't assigned.
:cbellini, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Comment 3•2 years ago
|
||
We should bump up the expiration version and get data-renew review on that.
Updated•2 years ago
|
| Assignee | ||
Comment 4•2 years ago
|
||
I don't understand what needs to be done for 122 when this probe expires in 123?
Comment 5•2 years ago
|
||
The probe expires with the switch of the development to version 123. Preferably, the probe gets extended or removed by the end of the 122 Nightly development, or if it shall be measured for 122 but not for 123, a patch must be available before the day of the version increase to 123, and RelEng or code sheriffs can land it to fix the permanent failure from the expired telemetry probe.
Comment 6•2 years ago
|
||
This is a reminder regarding comment #2!
The bug is marked as tracked for firefox122 (nightly). We have limited time to fix this, the soft freeze is in 10 days. However, the bug still isn't assigned.
Comment 7•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 8•2 years ago
|
||
Comment on attachment 9366852 [details]
extend-probes.txt
Data Collection Renewal Review (to be filled by Data Stewards)
- Is the provided Data Collection Review complete, correct, and data-review+ by a Data Steward?
yes
- Is the data collection covered by the existing Firefox Privacy Notice?
yes
Result
data-review+
Updated•2 years ago
|
Comment 9•2 years ago
|
||
:cbellini the Fx122 Merge Day is next week on 2023-12-18, central will be bumped to 123. A reminder that this needs to be addressed before then.
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
| bugherder | ||
Description
•