Remove or update probes expiring in Firefox 94: telemetry.*
Categories
(Toolkit :: Telemetry, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox-esr91 | --- | unaffected |
firefox91 | --- | unaffected |
firefox92 | --- | unaffected |
firefox93 | + | verified |
People
(Reporter: telemetry-probes, Assigned: chutten)
References
Details
(Whiteboard: [probe-expiry-alert])
Attachments
(2 files)
The following Firefox probes will expire in the next major Firefox nightly release: version 94 [1].
telemetry.state_file_save_errors
telemetry.generated_new_client_id
telemetry.loaded_client_id_doesnt_match_pref
telemetry.state_file_read_errors
telemetry.using_pref_client_id
telemetry.removed_client_ids
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•3 years ago
|
||
Comment 2•3 years ago
|
||
^ Linked pr is not for this bug, I linked the wrong one
Comment 3•3 years ago
|
||
[Tracking Requested - why for this release]: The xpcshell test toolkit/components/telemetry/tests/unit/test_client_id.js depends on it.
Assignee | ||
Comment 4•3 years ago
|
||
Yup, all these can, should, and will be removed now that investigations into spurious client_id generation have tapered off.
Updated•3 years ago
|
Assignee | ||
Comment 5•3 years ago
|
||
Comment 7•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Description
•