add telemetry data for DoH usage
Categories
(Core :: Networking, enhancement, P1)
Tracking
()
People
(Reporter: nhi, Assigned: tdsmith)
Details
(Whiteboard: [necko-triaged][trr])
Attachments
(3 files)
|
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
|
1.93 KB,
text/plain
|
teon
:
data-review+
|
Details |
|
56 bytes,
text/x-github-pull-request
|
Details | Review |
add new telemetry data for DoH rollout
:tdsmith, please add a comment here if you need new probes to be implemented. (we have pref network.trr.mode for whether DoH is enabled or not)
| Reporter | ||
Updated•7 years ago
|
| Assignee | ||
Comment 1•7 years ago
|
||
I normally shouldn't own telemetry implementations, but I agree that exposing network.trr.mode to telemetry is what we need to do, it should be a one-line change, and I know how to do it, so I'm happy to take this.
| Assignee | ||
Comment 2•7 years ago
|
||
Add the network.trr.mode pref, which reflects whether DNS over HTTPS is enabled or not, to the telemetry environment.
| Assignee | ||
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
| Assignee | ||
Comment 5•7 years ago
|
||
(In reply to Teon Brooks [:teon] from comment #4)
I just have a question about the documentation, do preferences in the
telemetry environment get added to one of the definitions files?
Hi Teon,
Thanks for the question! They do not.
The fact that userPrefs are collected is described here: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/environment.html#userprefs
There is no explicit documentation for most of the collected preferences, short of being listed in TelemetryEnvironment.jsm.
bug 1330856 exists to capture userPreference collection in a separate metadata file, which would facilitate the documentation plumbing. (I just opened bug 1567948 this morning to capture the need and then discovered the older bug.)
Some recent bugs with data-review for this mechanism include bug 1558856, bug 1514031, and bug 1485156.
Comment 6•7 years ago
|
||
Comment 8•7 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 9•7 years ago
|
||
Comment on attachment 9079487 [details]
Bug 1567607 - Expose network.trr.mode to telemetry
Beta/Release Uplift Approval Request
- User impact if declined: No direct impact. We're hoping to deliver DNS over HTTPS to some audiences during the 69 cycle and this patch, which collects the value of the pref that controls TRR state, will help us understand how users are engaging with TRR.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Not risky; adds a pref to a list of prefs to report in the telemetry environment.
- String changes made/needed:
Comment 10•7 years ago
|
||
Comment on attachment 9079487 [details]
Bug 1567607 - Expose network.trr.mode to telemetry
Adds a Telemetry probe for the network.trr.mode pref. Approved for 69.0b8.
Comment 11•7 years ago
|
||
| bugherder uplift | ||
Comment 12•7 years ago
|
||
Description
•