The W3C WebRTC Working Group recently announced that googMetrics will no longer be exposed in the WebRTC standard API. Talks are ongoing as to an alternative method to expose experimental metrics for developer use.
Chrome is in the process of providing a reliable path to deprecate googMetrics use. In order to remove these experimental stats, Google Chrome took them out once the getStats() API was transitioned from a callback-based to a promise-based API. This transition took place as of Chrome v.58, and meets W3C compliance in the promise-based getStats() API. For those relying on googMetrics, the callback-based getStats() API still returns them, however, none of the newly implemented metrics are reported by the old API.
It is important that callstats.io follows the W3C compliance standards in order to contribute to the unification of statistics across browsers, and therefore improve and help mature monitoring and reporting.
There is no doubt that new, promise-based statistics are much more performant and meet compliance standards. However, we are unable to fully retire callback-based statistics until remote reports are available in Chrome, as otherwise certain metrics will not be available. For example, this could limit measurements such as RTT and others.
Please report missing statistics to the webrtc-stats Github repo. For existing, browser-specific missing statistics, please review the following list of links and star ⭐ the bugs if you want to help move the discussion forward.