Closed Bug 1694949 Opened 4 years ago Closed 4 years ago

Add event telemetry containing failure reasons that lead to TRR confirmation failure

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
88 Branch
Tracking Status
firefox87 --- fixed
firefox88 --- fixed

People

(Reporter: valentin, Assigned: valentin)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(2 files)

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.

Attached file request-1694949.md
Attachment #9206117 - Flags: data-review?(tdsmith)

Comment on attachment 9206117 [details]
request-1694949.md

  1. 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.

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

Yes, the Firefox telemetry opt-out.

  1. If the request is for permanent data collection, is there someone who will monitor the data over time?

Valentin will monitor it.

  1. 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.

  1. Is the data collection request for default-on or default-off?

-On.

  1. 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.

  1. Is the data collection covered by the existing Firefox privacy notice?

Yes.

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

No.

  1. Does the data collection use a third-party collection tool?

No.

Attachment #9206117 - Flags: data-review?(tdsmith) → data-review+
Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/f62e7b312fa6 Add event telemetry containing failure reasons that lead to TRR confirmation failure r=nhnt11,dragana,necko-reviewers
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch

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:
Attachment #9205697 - Flags: approval-mozilla-beta?

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

Attachment #9205697 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: