Remove or update probes expiring in Firefox 100: BROWSER_ATTRIBUTION_ERRORS before Gecko version increases to 100 on 2022-03-08
Categories
(Firefox :: Messaging System, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox97 | --- | unaffected |
firefox98 | --- | unaffected |
firefox99 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: emcminn)
References
Details
(Whiteboard: [probe-expiry-alert])
Attachments
(2 files)
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/plain
|
jhirsch
:
data-review+
|
Details |
The following Firefox probes will expire in the next major Firefox nightly release: version 100 [1].
BROWSER_ATTRIBUTION_ERRORS
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
|
||
NI @andrei to help triage and should this probe be made indefinite.
Comment 2•3 years ago
|
||
Synched up with @andrei and as recommended in previous extension in https://bugzilla.mozilla.org/show_bug.cgi?id=1700826#c11, we will like to keep this probe indefinite.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
Assignee | ||
Comment 4•3 years ago
|
||
Comment 5•3 years ago
|
||
@nalexander I would like to make case for keeping this telemetry for indefinite as this provides info on if attribution is working as expected in wild and attribution data is reliable to use in targeting. Will be great to get your feedback. Thanks
https://searchfox.org/mozilla-central/source/browser/components/attribution/AttributionCode.jsm#303
Comment 6•3 years ago
|
||
@emcminn might need to flag one of Data Stewards as well for data-review https://wiki.mozilla.org/Data_Collection Thanks
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Comment 7•3 years ago
|
||
(In reply to Punam Dahiya [:pdahiya] from comment #5)
@nalexander I would like to make case for keeping this telemetry for indefinite as this provides info on if attribution is working as expected in wild and attribution data is reliable to use in targeting. Will be great to get your feedback. Thanks
https://searchfox.org/mozilla-central/source/browser/components/attribution/AttributionCode.jsm#303
Agreed. Thanks for doing the work here, :emcminn.
Comment 8•3 years ago
|
||
Tracking because browser/components/attribution/test/browser/browser_AttributionCode_* tests use the probe.
Comment 9•3 years ago
|
||
Comment on attachment 9263851 [details]
data_review_1754646.txt
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.
Comment 10•3 years ago
|
||
Comment 11•3 years ago
|
||
bugherder |
Description
•