Closed Bug 1923031 Opened 1 month ago Closed 1 month ago

Can we avoid recording networking.http3_enabled on content processes?

Categories

(Core :: Networking: HTTP, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
133 Branch
Tracking Status
firefox133 --- fixed

People

(Reporter: florian, Assigned: omansfeld)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

The networking.http3_enabled telemetry scalar landed in bug 1652104. It is recorded in both the parent process and content processes. This is annoying when trying to migrate scalars to Glean, as the Boolean metric type in Glean is only supported in the parent process.

Is recording this information on child processes really useful? Isn't it controlled by the value of a preference, and always the same on the parent end child processes?

The code recording the data is at https://searchfox.org/mozilla-central/rev/b546e74055186bb387ed7db9079374e1e7e0b88e/netwerk/protocol/http/nsHttpHandler.cpp#413-414

Flags: needinfo?(acreskey)

Yes, we definitely can avoid recording this in the child process.

Oskar, would you like to take this bug?
Thanks.

Flags: needinfo?(acreskey) → needinfo?(omansfeld)
Severity: -- → N/A
Type: defect → enhancement
Priority: -- → P2
Whiteboard: [necko-triaged]

(In reply to Kershaw Chang [:kershaw] from comment #1)

Yes, we definitely can avoid recording this in the child process.

Oskar, would you like to take this bug?
Thanks.

Hey, yes, I'll take a look!

Flags: needinfo?(omansfeld)
Assignee: nobody → omansfeld
Pushed by archaeopteryx@coole-files.de: https://hg.mozilla.org/integration/autoland/rev/708cac00604e Moved the NETWORKING_HTTP3_ENABLED telemetry scalar to only be recorded in the parent process. r=necko-reviewers,kershaw
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: