do we need a log callback function of webrtc native log in browser?

[bdrtc]

Background

we know webrtc provide getStats api for developer debug call, but sometimes this approach is insufficient from a developer perspective when debug online problem, webrtc native have a lot of log and disabled by default in browser, chrome provide command line log arguments to active native log but not others, sometimes developer need those webrtc native log to analize online problem, Especially mobile browsers are more fragmented, and there is no way to enable webrtc native logs in these browsers to analyze some compatibility issues.

Request
The request here is to be able to add a log callback function to RTCPeerConnection to print webrtc native log, and add log level configure to RtcConfiguration

i open it as start here, developers with the same pain points/requirements can discuss here.

[alvestrand]

I would greatly enjoy having a standard log facility.

The difficulty with proposing anything here is that logs often need to provide information that exposes internal implementation details - this means that the content of the log is unlikely to be consistent enough for standardization; two browsers will not produce identical logs on the identical sequence of events.

How to solve this?

[bdrtc]

I think maybe we do not need standard the content of log , it just export the webrtc native raw logs like below as bridge, and the log level also consistent with the built-in log level of webrtc, what's more, log level should disabled/error devel by default.