Remove or update probes expiring in Firefox 112: blocklist.mlbf_* before Gecko version gets increased to 112 on 2023-02-13
Categories
(Toolkit :: Blocklist Implementation, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox109 | --- | unaffected |
firefox110 | --- | unaffected |
firefox111 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: robwu)
References
Details
(Whiteboard: [probe-expiry-alert])
Attachments
(3 files)
The following Firefox probes will expire in the next major Firefox nightly release: version 112 [1].
blocklist.lastModified_rs_addons
blocklist.lastModified_rs_addons_mlbf
blocklist.mlbf_enabled
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.
Comment 1•1 year ago
|
||
I talked with Luca, he will take care of this shortly.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 3•1 year ago
|
||
Assignee | ||
Comment 4•1 year ago
|
||
The set of notification_emails has been made consistent/identical across
all blocklist-related telemetry, to ensure that only one Bugzilla ticket
will be filed for future expiration bugs.
Comment 5•1 year ago
|
||
Comment on attachment 9313246 [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
Result
data-review+
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
|
||
The bug is marked as tracked for firefox111 (nightly). However, the bug still has low severity.
:Gijs, could you please increase the severity for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit auto_nag documentation.
Updated•1 year ago
|
Pushed by rob@robwu.nl: https://hg.mozilla.org/integration/autoland/rev/b7f3b82d5888 Update expiration of blocklist probes + notification_emails r=rpl
Comment 9•1 year ago
|
||
bugherder |
Comment 10•1 year ago
|
||
The expiration version for mlbf_stash_time_oldest
did not get bumped, test still fails: https://searchfox.org/mozilla-central/rev/d0cd6a42de9cbacd6d8f3253e2edc18076386282/toolkit/components/telemetry/Scalars.yaml#6466
Assignee | ||
Comment 11•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Comment 12•1 year ago
|
||
Pushed by rob@robwu.nl: https://hg.mozilla.org/integration/autoland/rev/4224cf6c202d Bump expiration of mlbf_stash_time_oldest r=rpl
Comment 13•1 year ago
|
||
bugherder |
Description
•