Improve the telemetry for the HTTP3 connection closing reasons
Categories
(Core :: Networking: HTTP, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox87 | --- | fixed |
People
(Reporter: dragana, Assigned: dragana)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
2.67 KB,
text/plain
|
mmccorquodale
:
data-review+
|
Details |
| Assignee | ||
Comment 1•5 years ago
|
||
neqo now exposes a better info about the close reason and should use it.
| Assignee | ||
Comment 2•5 years ago
|
||
| Assignee | ||
Comment 3•5 years ago
|
||
Comment 4•5 years ago
|
||
Comment on attachment 9199281 [details]
request_1688091.md
-
Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
This will be documented in the probe dictionary. -
Is there a control mechanism that allows the user to turn the data collection on and off?
Users can opt out of telemetry. -
If the request is for permanent data collection, is there someone who will monitor the data over time?
Dragana Damjanovic will monitor. -
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 Data. -
Is the data collection request for default-on or default-off?
Default on. -
Does the instrumentation include the addition of any new identifiers?
No new identifiers. -
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.
data-review +
Comment 6•5 years ago
|
||
| bugherder | ||
Description
•