Remove or update probes expiring in Firefox 82: COOKIE_PURGING_*
Categories
(Core :: Privacy: Anti-Tracking, task)
Tracking
()
People
(Reporter: telemetry-probes, Assigned: englehardt)
References
Details
(Whiteboard: [probe-expiry-alert])
Attachments
(2 files)
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
jcristau
:
approval-mozilla-release-
|
Details | Review |
4.20 KB,
text/plain
|
tdsmith
:
data-review+
|
Details |
The following Firefox probes will expire in the next major Firefox nightly release: version 82 [1].
COOKIE_PURGING_ORIGINS_PURGED
COOKIE_PURGING_TRACKERS_WITH_USER_INTERACTION
COOKIE_PURGING_TRACKERS_USER_INTERACTION_REMAINING_DAYS
COOKIE_PURGING_DURATION_MS
COOKIE_PURGING_INTERVAL_HOURS
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 #fx-metrics 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•4 years ago
|
||
Steve, if we decide to extend the metrics, I'll ask Tim to help create a patch.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 2•4 years ago
|
||
Assignee | ||
Comment 3•4 years ago
|
||
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Comment on attachment 9167757 [details] bug1656134.txt Great, thanks for the request. 1) Is there or will there be **documentation** that describes the schema for the ultimate data set in a public, complete, and accurate way? Yes, in the probe definition files and the [Probe Dictionary](https://probes.telemetry.mozilla.org/). 2) Is there a control mechanism that allows the user to turn the data collection on and off? Yes, the [Firefox telemetry opt-out](https://support.mozilla.org/en-US/kb/share-data-mozilla-help-improve-firefox). 3) If the request is for permanent data collection, is there someone who will monitor the data over time? No; temporary collection. 4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 2, interaction data. 5) Is the data collection request for default-on or default-off? Default-on. 6) Does the instrumentation include the addition of **any *new* identifiers** (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)? No. 7) Is the data collection covered by the existing Firefox privacy notice? Yes. 8) Does there need to be a check-in in the future to determine whether to renew the data? englehardt is responsible for renewing the collection as necessary. 9) Does the data collection use a third-party collection tool? No.
Pushed by senglehardt@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c1513a7d713c Extend COOKIE_PURGING_* probes to Firefox 88 and enable in release; r=timhuang,tdsmith, data-review=tdsmith
Comment 6•4 years ago
|
||
bugherder |
Assignee | ||
Comment 7•4 years ago
|
||
Comment on attachment 9167754 [details]
Bug 1656134 - Extend COOKIE_PURGING_* probes to Firefox 88 and enable in release; r=timhuang, data-review=tdsmith
Beta/Release Uplift Approval Request
- User impact if declined: This Telemetry is needed in Firefox release to inform the slow rollout of the cookie purging feature that started in Firefox 79. See https://experimenter.services.mozilla.com/experiments/tracker-cookie-purging/. (The probes were accidentally set to pre-release only). If declined for release the rollout will be on hold until the 80 cycle. If declined for beta the rollout will be on hold until the 81 cycle.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): No user-facing impact. The Telemetry probes have been in nightly/beta for a cycle with no issues.
- String changes made/needed: none
Comment 8•4 years ago
|
||
Comment on attachment 9167754 [details]
Bug 1656134 - Extend COOKIE_PURGING_* probes to Firefox 88 and enable in release; r=timhuang, data-review=tdsmith
approved for 80.0b5
Comment 9•4 years ago
|
||
bugherder uplift |
Comment 10•4 years ago
|
||
Comment on attachment 9167754 [details]
Bug 1656134 - Extend COOKIE_PURGING_* probes to Firefox 88 and enable in release; r=timhuang, data-review=tdsmith
80 ships next week and there are no plans for a 79 dot release
Updated•4 years ago
|
Description
•