-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Edge] pc.getStats(): no way to get usable and needed stats #523
Comments
The bad news is that collected stats are not accurate and they do not expose real values. For example:
I don't think this is usable at all. |
We need these things AFAIS:
If we can't get some of them, that's ok, lets hope they are added eventually to Edge. |
More problems:
|
Replying to @saghul's comment after checking everything:
Unfeasible. Edge does not set
Unfeasible. Edge does not set
Unfeasible. Edge does not add |
Fixed in 6437dfa |
getStats()
has been added to the Edge'sRTCPeerConnection
shim. Basically it's achieved by collecting all the stats from the allRTCIceTransport
,RTCRtpSender
andRTCRtpReceiver
instances internally handled by theRTCPeerConnection
object.Below the results of
pc.getStats()
in Edge after 1 minute (more or less) in a call with a Chrome browser (which was running in a computer with a hardcoded 25% of up/down packet lost):The text was updated successfully, but these errors were encountered: