Intent to Experiment: WebRTC Diagnostic Logging API

91 views
Skip to first unread message

Chromestatus

unread,
Jun 23, 2026, 11:58:51 AM (3 days ago) Jun 23
to blin...@chromium.org, gui...@google.com
Contact emails
gui...@google.com

Explainer
https://github.com/WICG/webrtc-diagnostic-logging/blob/main/explainer.md

Specification
https://wicg.github.io/webrtc-diagnostic-logging

Summary
API for WebRTC diagnostic logging. This API allows an application to opt in to diagnostic logging. These logs contain information about the WebRTC activity by the application and are useful for local debugging or to file bugs. Logs can be optionally uploaded out of band to the browser vendor and can be used for diagnosing bugs. The application gets an ID that can be attached to a bug report, similar to crashes. Diagnostic logs are enabled via an enterprise policy called WebRtcDiagnosticLogCollectionAllowedForOrigins.

Blink component
Blink>WebRTC

Web Feature ID
No information provided

TAG review
No information provided

TAG review status
Pending

Goals for experimentation
We want to test to what extent the API properly supports the following use cases: * Allowing enterprises to collect diagnostic data about WebRTC in order to assist in debugging online problems * Collaborate with UA vendors to fix UA WebRTC bugs.

Risks


Interoperability and Compatibility
No information provided

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

No information provided


Ongoing technical constraints
No information provided

Debuggability
No information provided

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
No
Supported on desktop platforms.

Is this feature fully tested by web-platform-tests?
No


Flag name on about://flags
No information provided

Finch feature name
RTCDiagnosticLogging

Requires code in //chrome?
True

Tracking bug
https://crbug.com/481412281

Launch bug
https://launch.corp.google.com/launch/4419765

Estimated milestones
Shipping on desktop156
Origin trial desktop first150
Origin trial desktop last155


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5091582546149376?gate=5167223161356288

This intent message was generated by Chrome Platform Status.

Guido Urdaneta

unread,
Jun 24, 2026, 7:07:39 PM (2 days ago) Jun 24
to Chromestatus, blin...@chromium.org
Correction: The plan is to run the Origin Trial from 151 to 156.

Guido Urdaneta

unread,
Jun 25, 2026, 5:57:36 AM (19 hours ago) Jun 25
to Chromestatus, blin...@chromium.org
After discussing more internally, we prefer to stick to the original plan.
We request permission to experiment from 150 to 155.

Chris Harrelson

unread,
Jun 25, 2026, 4:13:49 PM (8 hours ago) Jun 25
to Guido Urdaneta, Chromestatus, blin...@chromium.org
LGTM

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BBuZxYacB70NsLrNnxB_A_Q3OQm3udrrc4Xkj8NrQhTWkdUGA%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages