Closed
Bug 1850367
Opened 2 years ago
Closed 2 years ago
Add telemetry probe in DNS code to understand if HTTPS RR is available
Categories
(Core :: Networking: DNS, task, P2)
Core
Networking: DNS
Tracking
()
RESOLVED
FIXED
119 Branch
| Tracking | Status | |
|---|---|---|
| firefox119 | --- | fixed |
People
(Reporter: kershaw, Assigned: kershaw)
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
2.51 KB,
text/plain
|
chutten
:
data-review+
|
Details |
No description provided.
| Assignee | ||
Comment 1•2 years ago
|
||
| Assignee | ||
Comment 2•2 years ago
|
||
Attachment #9350486 -
Flags: data-review?(chutten)
Comment 3•2 years ago
|
||
Comment on attachment 9350486 [details]
bug1850367_data_review.txt
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 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, :kershaw 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 the data collection use a third-party collection tool?
No.
Result: datareview+
Attachment #9350486 -
Flags: data-review?(chutten) → data-review+
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/039f50fd3165
Add telemetry for the availability of HTTPS RR, r=necko-reviewers,valentin
Comment 5•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox119:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•