1699523 - Key TRR skip reason probes by provider and split fallback probe into success and failure

Status: RESOLVED FIXED

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

Description

[(inactive) Nihanth Subramanya [:nhnt11]]

Currently we record TRR_SKIP_REASON_DNS_WORKED, which shows us the count of native lookups that succeeded after TRR was skipped, grouped by skip reason. We can currently infer the count of native lookups that failed by subtracting this from TRR_SKIP_REASON_TRR_FIRST, but it'd be nice to record it directly e.g. put DNS_WORKED together with this new measurement in one keyed histogram TRR_SKIP_REASON_NATIVE_FALLBACK or something.

Comment 1

[Valentin Gosu [:valentin] (he/him)]

Do you want to work on this?

Comment 2

[(inactive) Nihanth Subramanya [:nhnt11]]

Attachment: Bug 1699523 - Key TRR skip reason histograms by provider, split fallback into success and failure. r=#necko!

Comment 3

[(inactive) Nihanth Subramanya [:nhnt11]]

Keeping the needinfo because I need to request data review

Comment 4

[(inactive) Nihanth Subramanya [:nhnt11]]

Attachment: Data Review Request

Comment 5

[Chris H-C :chutten]

Comment on attachment 9214239 [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.

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, Nihanth 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+

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f5b433ddba98
Key TRR skip reason histograms by provider, split fallback into success and failure. r=necko-reviewers,valentin

Comment 7

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/mozilla-central/rev/f5b433ddba98