Add event telemetry containing failure reasons that lead to TRR confirmation failure
Categories
(Core :: Networking: DNS, enhancement, P1)
Tracking
()
People
(Reporter: valentin, Assigned: valentin)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
2.49 KB,
text/plain
|
tdsmith
:
data-review+
|
Details |
In Bug 1691408 we added some code that tracks the confirmation process. We know that a lot of times this happens because of multiple TRR failures in a row, but we don't know what caused those failures.
This bug is meant to record telemetry regarding those failures.
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
Comment 3•4 years ago
|
||
Comment on attachment 9206117 [details]
request-1694949.md
- Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
Yes, in the probe definition files and the Probe Dictionary.
- Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, the Firefox telemetry opt-out.
- If the request is for permanent data collection, is there someone who will monitor the data over time?
Valentin will monitor it.
- Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Cat 1, technical data.
- Is the data collection request for default-on or default-off?
-On.
- 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.
- 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.
- Does the data collection use a third-party collection tool?
No.
Comment 5•4 years ago
|
||
bugherder |
Assignee | ||
Comment 6•4 years ago
|
||
Comment on attachment 9205697 [details]
Bug 1694949 - Add event telemetry containing failure reasons that lead to TRR confirmation failure r=nhnt11,dragana
Beta/Release Uplift Approval Request
- User impact if declined: Not user visible.
- Is this code covered by automated tests?: Yes
- 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): Adds an extra string to the telemetry event containing a string representation of the failure reasons that trigger a TRR confirmation. This is necessary to evaluate if our confirmation process is optimal.
- String changes made/needed:
Comment 7•4 years ago
|
||
Comment on attachment 9205697 [details]
Bug 1694949 - Add event telemetry containing failure reasons that lead to TRR confirmation failure r=nhnt11,dragana
approved for 87.0b6
Comment 8•4 years ago
|
||
bugherder uplift |
Description
•