User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release) Build ID: 20140429030201 Steps to reproduce: used about:webrtc and getStats API to view information about WebRTC sessions Actual results: Received valuable information but not everything I was looking for Expected results: Apart from the stats already defined in the W3C spec, some useful additions to the getStats APIwould be: - Active ICE Candidate details like which candidate type is being used - Voice Activity and Audio level per SSRC and ideally per CSRC (per RFC6464 and 6465) - Video FrameRate&Resolution (as included in Chrome implementation) - RTT, packetloss & jitter (as included in Chrome implementation) - RTCP Packets/Bytes sent&recv Here are a few other metrics that we consider useful. We understand that they may be out of the scope of the getStats API even if some of them are already supported by Chrome's implementation: - CPU load - Audio Input and Output level

likely need breakdown like bug 964161 to prioritize which statistics to gather in 33 vrs 34

Assigning to Randell for bug breakdown

Mass change P3->P4 to align with new Mozilla triage process.

The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months. :jib, maybe it's time to close this bug?

The stats spec [1] has grown plenty of stats to cover this by now. [1] https://w3c.github.io/webrtc-stats/#dcstats-dict*