Closed
Bug 1714261
Opened 3 years ago
Closed 3 years ago
Remove or update probes expiring in Firefox 92: PRINT_INIT_TO_P*
Categories
(Toolkit :: Printing, task, P2)
Toolkit
Printing
Tracking
()
RESOLVED
FIXED
92 Branch
Tracking | Status | |
---|---|---|
firefox92 | --- | fixed |
People
(Reporter: telemetry-probes, Assigned: mstriemer)
References
Details
(Whiteboard: [probe-expiry-alert])
Attachments
(1 file)
The following Firefox probes will expire in the next major Firefox nightly release: version 92 [1].
PRINT_INIT_TO_PLATFORM_SENT_SETTINGS_MS
PRINT_INIT_TO_PREVIEW_DOC_SHOWN_MS
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.
Flags: needinfo?(jwatt)
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Assignee: nobody → mstriemer
Status: NEW → ASSIGNED
Assignee | ||
Updated•3 years ago
|
Severity: -- → S4
Priority: -- → P2
Pushed by mstriemer@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f92853efd0f5 Bump print perf telemetry r=jwatt
Comment 3•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox92:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 92 Branch
Updated•3 years ago
|
Flags: needinfo?(jwatt)
You need to log in
before you can comment on or make changes to this bug.
Description
•