Closed Bug 1470813 Opened 6 years ago Closed 6 years ago

TRR: add telemetry probe to enhance DNS_TRR_RACE

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: bagder, Assigned: bagder)

Details

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

Attachments

(2 files, 2 obsolete files)

The replacement probe, should add two "faster than 100" categories as well compared to the old version.
Comment on attachment 8987438 [details]
bug 1470813 - Telemetry::DNS_TRR_RACE2 adds two new categories

https://reviewboard.mozilla.org/r/252678/#review259624

data collection review too
Attachment #8987438 - Flags: review?(mcmanus) → review+
Request for data collection review: Telemetry::DNS_TRR_RACE2
Attachment #8987851 - Flags: review?(francois)
Comment on attachment 8987438 [details]
bug 1470813 - Telemetry::DNS_TRR_RACE2 adds two new categories

https://reviewboard.mozilla.org/r/252678/#review261410

::: toolkit/components/telemetry/Histograms.json:3265
(Diff revision 1)
>      "alert_emails": ["necko@mozilla.com", "dstenberg@mozilla.com"],
>      "expires_in_version": "never",
>      "kind": "categorical",
> -    "labels": ["TRRFasterBy50", "TRRFaster", "NativeFaster", "NativeFasterBy50"],
> -    "bug_numbers": [1434852],
> +    "labels": ["TRRFasterBy100", "TRRFasterBy50", "TRRFaster", "NativeFaster", "NativeFasterBy50",
> +               "NativeFasterBy100"],
> +    "bug_numbers": [1470813],

I'd suggest you keep the original bug number in this array so that it's easier to extract the history of this probe.
Comment on attachment 8987851 [details]
telemetry-dns_trr_race2.txt

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

Yes, in 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](https://wiki.mozilla.org/Firefox/Data_Collection)** 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 ON in pre-release channels only.

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)?

No.

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

Yes.

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

No, permanent.
Attachment #8987851 - Flags: review?(francois) → review+
(In reply to François Marier [:francois] from comment #4)

> I'd suggest you keep the original bug number in this array so that it's
> easier to extract the history of this probe.

Thanks will do! I wasn't sure what's considered the right thing there.
We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again.

hg error in cmd: hg rebase -s f2fc11a02538de25ca4da6fa2a0cb72206ae191b -d 2fafbc23c259: rebasing 471125:f2fc11a02538 "bug 1470813 - Telemetry::DNS_TRR_RACE2 adds two new categories r=mcmanus" (tip)
merging netwerk/dns/nsHostResolver.cpp
merging toolkit/components/telemetry/Histograms.json
warning: conflicts while merging toolkit/components/telemetry/Histograms.json! (edit, then use 'hg resolve --mark')
unresolved conflicts (see hg resolve, then hg rebase --continue)
We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again.

hg error in cmd: hg rebase -s 0dca4aec3e1eb519a0345f26900641b860a547ad -d 3928fa2e88ee: rebasing 471126:0dca4aec3e1e "bug 1470813 - Telemetry::DNS_TRR_RACE2 adds two new categories r=mcmanus" (tip)
merging netwerk/dns/nsHostResolver.cpp
merging toolkit/components/telemetry/Histograms.json
warning: conflicts while merging toolkit/components/telemetry/Histograms.json! (edit, then use 'hg resolve --mark')
unresolved conflicts (see hg resolve, then hg rebase --continue)
My mozreview skills fail me, so I'm attaching the rebased replacement patch here
Attachment #8987438 - Attachment is obsolete: true
Attachment #8989693 - Flags: review+
Keywords: checkin-needed
While try to apply this patch I get this error:

ccoroiu@ubuntu:~/mozilla-unified$ hg qimport bz://1470813
Fetching... done
Parsing... done
adding 1470813 to series file
renamed 1470813 -> 0001-bug-1470813-Telemetry-DNS_TRR_RACE2-adds-two-new-cat.patch
ccoroiu@ubuntu:~/mozilla-unified$ hg qpush 
applying 0001-bug-1470813-Telemetry-DNS_TRR_RACE2-adds-two-new-cat.patch
patching file toolkit/components/telemetry/Histograms.json
Hunk #1 FAILED at 3244
1 out of 1 hunks FAILED -- saving rejects to file toolkit/components/telemetry/Histograms.json.rej
patch failed, unable to continue (try -v)
patch failed, rejects left in working directory
errors during apply, please fix and qrefresh 0001-bug-1470813-Telemetry-DNS_TRR_RACE2-adds-two-new-cat.patch

Could you please take a look?
Flags: needinfo?(francois)
Keywords: checkin-needed
Flags: needinfo?(daniel)
Flags: needinfo?(francois)
Rebased. Clearly this patch was in a race with another one...
Attachment #8989693 - Attachment is obsolete: true
Flags: needinfo?(daniel)
Attachment #8989908 - Flags: review+
Keywords: checkin-needed
Pushed by apavel@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f0c99191daf9
Telemetry::DNS_TRR_RACE2 adds two new categories r=francois
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/f0c99191daf9
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: