Add telemetry for tcpByDefault Nimbus feature
Categories
(Core :: Privacy: Anti-Tracking, task, P1)
Tracking
()
People
(Reporter: pbz, Assigned: pbz)
References
Details
(Whiteboard: [fxatps-tcp] )
Attachments
(3 files)
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
2.87 KB,
text/plain
|
chutten
:
data-review+
|
Details |
We need a new scalar that keeps track of how many clients have the tcpByDefault
Nimbus feature enabled.
Once we have a separate probe to keep track of the feature state, we can remove the code that sets the rollout scalar to 3
here: https://searchfox.org/mozilla-central/rev/ea1234192518e01694a88eac8ff090e4cadf5ca4/browser/components/BrowserGlue.jsm#1742
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Depends on D145316
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Assignee | ||
Comment 4•2 years ago
|
||
[Tracking Requested - why for this release]:
We need this telemetry to support the TCP rollout in Fx 101
Comment 5•2 years ago
|
||
Comment on attachment 9274843 [details]
data-review-request.md
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.
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?
No. This collection will expire in Firefox 108.
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 the data collection use a third-party collection tool?
No.
Result: datareview+
Updated•2 years ago
|
Pushed by pzuhlcke@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/39f169b8d8b3 Add telemetry scalar to keep track of tcpByDefault feature state. r=anti-tracking-reviewers,bvandersloot https://hg.mozilla.org/integration/autoland/rev/5d9ba76fdbb4 Updates tests for tcpByDefault telemetry probe. r=anti-tracking-reviewers,timhuang
Updated•2 years ago
|
![]() |
||
Comment 7•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/39f169b8d8b3
https://hg.mozilla.org/mozilla-central/rev/5d9ba76fdbb4
Assignee | ||
Comment 8•2 years ago
|
||
Comment on attachment 9274793 [details]
Bug 1767415 - Add telemetry scalar to keep track of tcpByDefault feature state. r=#anti-tracking!
Beta/Release Uplift Approval Request
- User impact if declined: This telemetry is needed to support the Total Cookie Protection rollout in Fx 101 and onward.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: To be tested as part of https://mozilla-hub.atlassian.net/browse/QA-1482
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Telemetry only, no change in behavior.
- String changes made/needed:
- Is Android affected?: No
Assignee | ||
Updated•2 years ago
|
Comment 9•2 years ago
|
||
Comment on attachment 9274793 [details]
Bug 1767415 - Add telemetry scalar to keep track of tcpByDefault feature state. r=#anti-tracking!
Approved for 101.0b3.
Updated•2 years ago
|
Comment 10•2 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-beta/rev/f9c96e317d17
https://hg.mozilla.org/releases/mozilla-beta/rev/7919584a3184
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Description
•