PSA: Standardized stats in chrome://webrtc-internals/ in M75 (Now in Canary)

[Henrik Boström]

chrome://webrtc-internals/ now display stats from the standardized getStats() API and also allows downloading them ("Create dump").

The standardized API is the API that does not take a callback as argument but returns a promise that is resolved with an RTCStatsReport.

The stats are documented here: https://w3c.github.io/webrtc-stats/

(Only a handful of returned metrics have not been added to the main spec yet, these are publicly documented here: https://henbos.github.io/webrtc-provisional-stats/)

Because the standardized API is primarily based on accumulative metrics, averages can easily be calculated for any time interval by calling getStats() twice and dividing the difference with the difference in timestamp.

The chrome://webrtc-internals/ graphs and dumps include derived metrics like rates (based on total counters) and average audio level (based on root mean square values of total audio energy).

This page should aid developers migrating from the legacy (callback-based) getStats() API to the standardized and documented option, and help debugging applications with modern stats.

More standardized metrics are planned to be implemented for M76, see https://bugs.chromium.org/p/webrtc/issues/detail?id=10428 and BlockedOn issues for recent activity in this area.

If you are still relying on "goog" stats you are still able to view the legacy stats in chrome://webrtc-internals/ by using the drop-down menu at the top of the page. We want to deprecate the legacy API but have not announced a time-frame yet.

[Henrik Boström]

Higher resolution images:

https://groups.google.com/group/discuss-webrtc/attach/e9a580a167d7/Screenshot%20from%202019-04-26%2018-47-38.png?part=0.1&view=1

https://groups.google.com/group/discuss-webrtc/attach/e9a580a167d7/Screenshot%20from%202019-04-26%2018-49-27.png?part=0.2&view=1

[Sergio Garcia Murillo]

are the stat for bweforvideo going to be removed also? They are really important IMHO an there is nothing standard api that provides same information.

Best regards

Sergio

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/20aa0229-1896-44b2-b204-f5ff20ff8952%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Henrik Boström]

(Sorry for the delay in replying, for some reason this doesn't show up in my inbox)

See RTCIceCandidatePairStats.availableOutgoingBitrate on the appropriate candidate pair. This is the equivalent of "googAvailableSendBandwidth".

To unsubscribe from this group and stop receiving emails from it, send an email to discuss...@googlegroups.com.

[Henrik Boström]

There are more metrics planned too: https://bugs.chromium.org/p/webrtc/issues/detail?id=10428

[Sergio Garcia Murillo]

Thank you Henrik! that was what I was looking for.

To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/b40e991d-7eaa-4a06-a74c-a2563e859992%40googlegroups.com.