Closed
Bug 1645079
Opened 5 years ago
Closed 5 years ago
Remove or update probes expiring in Firefox 80: XCTO_NOSNIFF_TOPLEVEL_NAV_EXCEPTIONS
Categories
(Firefox :: General, task)
Firefox
General
Tracking
()
RESOLVED
FIXED
Firefox 79
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: telemetry-probes, Assigned: sstreich)
Details
(Whiteboard: [probe-expiry-alert])
Attachments
(1 file)
The following Firefox probes will expire in the next major Firefox nightly release: version 80 [1].
XCTO_NOSNIFF_TOPLEVEL_NAV_EXCEPTIONS
The following bugs are associated with the above probes: bug 1428473
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.
Flags: needinfo?(sstreich)
Assignee | ||
Comment 1•5 years ago
|
||
- c2ec766b798c
Updated•5 years ago
|
Assignee: nobody → sstreich
Status: NEW → ASSIGNED
Assignee | ||
Updated•5 years ago
|
Flags: needinfo?(sstreich)
Pushed by cbrindusan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e94d68cd516a
backout XTCO Telemetry r=ckerschb
Comment 3•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 79
You need to log in
before you can comment on or make changes to this bug.
Description
•