Report fission.autostart pref telemetry using RECORD_DEFAULTPREF_VALUE for all pref branches
Categories
(Core :: DOM: Navigation, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox77 | --- | fixed |
People
(Reporter: cpeterson, Assigned: annyG)
References
Details
Attachments
(2 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
2.62 KB,
text/plain
|
chutten
:
data-review+
|
Details |
tdsmith says "Using the RECORD_PREF_VALUE mechanism in TelemetryEnvironment.jsm means that a value for this pref will only be recorded in a ping if it is set on the user branch."
To simplify telemetry comparisons for our Fission A/B experiments, we should probably start reporting this value in telemetry for all users with RECORD_DEFAULTPREF_VALUE
instead of RECORD_PREF_VALUE
. IIUC, this change will make the fission.autostart
pref value queryable for all users, regardless of whether they've set the pref manually or when we change the default value.
Comment 1•4 years ago
|
||
(Not exactly sure where this bug should go. It should be in the component of the team who wants to own this collection)
Comment 2•4 years ago
|
||
Navigation's probably a better component for generic Fission bugs.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 3•4 years ago
|
||
Move Fission telemetry probe bugs from M5 dogfooding milestone to M6 Nightly.
Reporter | ||
Comment 4•4 years ago
|
||
We'll want to fix this pref bug soon to make Fission telemetry comparisons (ad hoc on TMO and in A/B experiments) easier.
Reporter | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
Assignee | ||
Comment 6•4 years ago
|
||
Will request a data review once my smoke test on try is done. Local testing was successful!
Assignee | ||
Comment 7•4 years ago
|
||
Comment 8•4 years ago
|
||
Comment on attachment 9138576 [details] data-review-request DATA COLLECTION REVIEW RESPONSE: Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate? Yes. This collection is documented in its [in-tree documentation](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/data/environment.html#userprefs). Is there a control mechanism that allows the user to turn the data collection on and off? Yes. This collection is Telemetry so can be controlled through Firefox's Preferences. If the request is for permanent data collection, is there someone who will monitor the data over time? Yes, :annyG is responsible. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 1, Technical. Is the data collection request for default-on or default-off? Default on for all channels. Does the instrumentation include the addition of any new identifiers? No. Is the data collection covered by the existing Firefox privacy notice? Yes. Does there need to be a check-in in the future to determine whether to renew the data? No. This collection is permanent. --- Result: datareview+
Pushed by agakhokidze@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0640647b2fc6 Report fission.autostart pref telemetry using RECORD_DEFAULTPREF_VALUE for all pref branches, r=NeilDeakin
Comment 10•4 years ago
|
||
bugherder |
Description
•