Closed Bug 1460589 Opened 2 years ago Closed 2 years ago

TRR: add telemetry probe for TRR vs Native success/failure rate


(Core :: Networking: DNS, enhancement, P1)




Tracking Status
firefox62 --- fixed


(Reporter: bagder, Assigned: bagder)


(Whiteboard: [necko-triaged][trr])


(2 files)

No description provided.
How about this approach? It only adds a value if both native *and* TRR were used, but it stores all 4 different result combos.
Attachment #8974699 - Flags: review?(mcmanus)
Comment on attachment 8974699 [details] [diff] [review]

Review of attachment 8974699 [details] [diff] [review]:

obv need data review too thanks
Attachment #8974699 - Flags: review?(mcmanus) → review+
Comment on attachment 8974718 [details]
Request for data collection review: DNS_TRR_COMPARE

1) Is there or will there be **documentation** that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes, Histograms.json.

2) Is there a control mechanism that allows the user to turn the data collection on and off?

Yes, telemetry setting.

3) If the request is for permanent data collection, is there someone who will monitor the data over time?**

Yes, Daniel Stenberg.

4) Using the **[category system of data types](** on the Mozilla wiki, what collection type of data do the requested measurements fall under?  **

Category 1.

5) Is the data collection request for default-on or default-off?

Default off on release.

6) Does the instrumentation include the addition of **any *new* identifiers** (whether anonymous or otherwise; e.g., username, random IDs, etc.  See the appendix for more details)?


7) Is the data collection covered by the existing Firefox privacy notice?


8) Does there need to be a check-in in the future to determine whether to renew the data?

No, permanent.
Attachment #8974718 - Flags: review?(francois) → review+
Keywords: checkin-needed
Pushed by
Add DNS vs TRR success/fail telemetry counter. r=mcmanus
Keywords: checkin-needed
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in before you can comment on or make changes to this bug.