Re: [webrtc-extensions] do we need a log callback function of webrtc native log in browser? (#124)

I think the Reporting API is something different.

For me, the question is why the application needs to collect low level logs from the Webrtc stack itself ? Because having these logs need to have a super customer support guy who can assist the end-user to start chrome in debug mode and to get the right file...

The short answer is that at application (web) level, we suffer from a lack of information to help investigating users issues like why it takes 10 seconds to hear the remote side, why the first call of the day don't work, why I can't hear the remote side at all...

Distinguishing an application issue from a browser, system, network or remote side issue need more logs that the ones that can be captured at the web level. Using Electron (need a restart) or a native mobile application, we have the possibility to automatically collect these logs when an issue occurs. This helps a lot to confirm the origin or an issue or at least to close some doors.

The answer could be to have more information that goes to the application itself (a way to subscribe to a subset or events or errors like error 10053). Those could be standardized. Or a better way to collect all these existing logs (like on native) from a Web application.


-- 
GitHub Notification of comment by oanguenot
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/124#issuecomment-5140080128 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 31 July 2026 06:38:27 UTC