-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
WebRTC: Statistics similar to chrome://webrtc-inernals. #2149
Comments
What information is needed for the webrtc streaming client? |
I want to monitor the information of the push streaming client and the pull streaming client, but the current httpAPI cannot monitor the webrtc pull streaming client and does not return the corresponding information, while the RTMP can. Is there a problem with my configuration, or is this feature not currently supported? Please help. |
It is not currently supported. I have modified the code myself to add this feature. I will submit a PR next week, and you can try merging it into your code. |
Good job |
@siyangbing Please take a look at this PR #2169, which only handles webrtc pull streaming. The same principle applies to push streaming, and you can modify the code yourself. |
@siyangbing Buy one get one free, and add another feature for kbps traffic statistics when playing webrtc (add kbps statistic for webrtc play 2b2b6c1) |
Thank you so much, brother, you've been a great help. |
See #1657 |
SRS will support statistics for WebRTC by both HTTP API and Prometheus exporter see #2899 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
No description provided.
The text was updated successfully, but these errors were encountered: