Closed
Bug 1968510
Opened 2 months ago
Closed 2 months ago
Collect telemetry on HTTP connection types used for transaction dispatch
Categories
(Core :: Networking: HTTP, task, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
141 Branch
| Tracking | Status | |
|---|---|---|
| firefox141 | --- | fixed |
People
(Reporter: kershaw, Assigned: kershaw)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
Before starting to implement HappyEveball v3, it'd good to add some probes to better understand how HTTP transactions are dispatched to connections.
We should add telemetry to record the type of connection each transaction is assigned to. This includes:
- Connection type (proxy, HTTP/1.1, HTTP/2, HTTP/3)
- The IP used by the connection is IPv4 or IPv6
|
Assignee | |
Comment 1•2 months ago
|
||
|
||
Updated•2 months ago
|
Assignee: nobody → kershaw
Status: NEW → ASSIGNED
Pushed by kjang@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/5c2b9de5ceaf
https://hg.mozilla.org/integration/autoland/rev/d20583b1d2f9
Record IP address family when a transaction is dispatched, r=necko-reviewers,sunil
|
||
Comment 3•2 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
status-firefox141:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 141 Branch
|
||
Updated•1 month ago
|
QA Whiteboard: [qa-triage-done-c142/b141]
You need to log in
before you can comment on or make changes to this bug.
Description
•