Remove or update probes expiring in Firefox 122: blocklist.* before Gecko version gets increased to 122 on 2023-11-20
Categories
(Toolkit :: Blocklist Implementation, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox119 | --- | unaffected |
| firefox120 | --- | unaffected |
| firefox121 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: robwu)
References
Details
(Whiteboard: [probe-expiry-alert][addons-jira])
Attachments
(2 files)
|
1.13 KB,
text/plain
|
travis_
:
data-review+
|
Details |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
The following Firefox probes will expire in the next major Firefox nightly release: version 122 [1].
blocklist.addonBlockChange#addonBlockChange
blocklist.lastModified_rs_addons
blocklist.lastModified_rs_addons_mlbf
blocklist.mlbf_enabled
blocklist.mlbf_source
blocklist.mlbf_generation_time
blocklist.mlbf_stash_time_oldest
blocklist.mlbf_stash_time_newest
What to do about this:
- If one, some, or all of the metrics are no longer needed, please remove them from their definitions files (Histograms.json, Scalars.yaml, Events.yaml).
- If one, some, or all of the metrics are still required, please submit a Data Collection Review [2] and patch to extend their expiry. There is a shorter form for data collection renewal [3].
If you have any problems, please ask for help on the #data-help Slack channel or the #telemetry Matrix room at https://chat.mozilla.org/#/room/#telemetry:mozilla.org. We'll give you a hand.
Your Friendly, Neighborhood Telemetry Team
[1] https://wiki.mozilla.org/Release_Management/Calendar
[2] https://wiki.mozilla.org/Firefox/Data_Collection
[3] https://github.com/mozilla/data-review/blob/master/renewal_request.md
This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Rob / Mathieu, do you think we still need these probes?
| Assignee | ||
Comment 2•2 years ago
|
||
Yes. I'll take care of renewal.
Updated•2 years ago
|
| Assignee | ||
Comment 4•2 years ago
|
||
Data review request; Compared to previous blocklist probe requests, blocklist.mlbf_enabled has now been omitted because it was removed in bug 1820155 (which I requested during review).
Comment 5•2 years ago
|
||
Comment on attachment 9360649 [details]
renewal_request-blocklist-v3-usage-telemetry.md
Data Collection Renewal Review
- 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
Comment 6•2 years ago
|
||
Tracking because at least toolkit/mozapps/extensions/test/xpcshell/rs-blocklist/test_blocklist_mlbf_telemetry.js checks for this.
Comment 7•2 years ago
|
||
The bug is marked as tracked for firefox121 (nightly). We have limited time to fix this, the soft freeze is in 14 days. However, the bug still has low priority.
:mixedpuppy, could you please increase the priority for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 8•2 years ago
|
||
And remove the mention of the blocklist.mlbf_enabled scalar, since its
implementation was removed in bug 1820155. Note that mlbf_enabled
defaulted to true since Firefox 78 (bug 1631018), and that the pref to
revert it was removed in Firefox 91 (bug 1706391). The latter was
desktop-only, but the telemetry wasn't sent on Android anyway. The
Glean-based telemetry was introduced in Firefox 115 (bug 1820155) along
with the removal of mlbf_enabled.
Comment 10•2 years ago
|
||
| bugherder | ||
Description
•