Skip to content
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

Expose the usefull experimental stats to a JavaScript layer #609

Closed
Doreapp opened this issue Jul 6, 2021 · 3 comments
Closed

Expose the usefull experimental stats to a JavaScript layer #609

Doreapp opened this issue Jul 6, 2021 · 3 comments
Assignees

Comments

@Doreapp
Copy link

Doreapp commented Jul 6, 2021

Some statistics, such as freezeCount, totalFreezeDuration, pauseCount and totalPauseDuration are only available from a native level or through webrtc-internals.

Those are documented as webrtc-provisional-stats and seem to be implemented some time ago (according to this commit in February 2019)

I would love to be able to access these metrics from a JavaScript level, ideally from the getStats function.

@vr000m
Copy link
Contributor

vr000m commented Aug 13, 2021

The experimental stats should be available via getStats. In the actual browser implementation, it might be available via origin-trials. @henbos can throw some light on the status of the Freeze* metrics in Chrome.

@henbos
Copy link
Collaborator

henbos commented Aug 23, 2021

We have exposed experimental metrics in the past in origin trials but I don't think these metrics are tied to any ongoing experiments afaik.

Most likely these metrics were added by native users due to "probably being useful" but not having any strong justification or backing by the spec. So either we never followed up on them after them having been proven useful or alternaively maybe they weren't useful.

But probably we just forgot about them :)

@henbos
Copy link
Collaborator

henbos commented Sep 27, 2022

This was being asked for again in #695, let's close this one as a dupe, I cc'd someone on that other issue to shed some light on this. I'm not opposed to exposing these metrics

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants