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

Add more information to PeerConnectionAnalyzer logs #14442

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

danxuliu
Copy link
Member

@danxuliu danxuliu commented Feb 17, 2025

Follow up to #14095

Requires #14419 (as otherwise there would be conflicts once that one is merged)

The additional information in the logs should help to debug connection warnings and find out if they were legit or false positives that still need to be fixed.

Although it would not be strictly needed to backport this to 29 and 30 it might help to avoid conflicts with backports of future fixes.

TODO

  • Log RTC stats also for receiver connections (the PeerConnectionAnalyer is not currently enabled for receiver connections, but it will be to detect stalled receiver connections and restart them)

The stats were supposed to be distributed once they had changed, but
in practice they were always distributed, as the packet count is
absolute rather than relative. Nevertheless, if the packet count did not
change distributing them would have no effect. The problem could appear
in the (rare) case of the timestamps not being updated three times in a
row, as the distribution algorithm failed if the final timestamp was the
same as the initial timestamp (causing NaN to be set for the packets and
packets lost).

Due to all that now the staged stats are always distributed before being
commited (which is still done when the stats stalled for two seconds),
although the distribution exits early if the timestamps did not change.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Otherwise it was not possible to know if the logged stats belonged to
the video or screen peer.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
The raw RTC stats provide additional information that is sometimes
needed to debug the connection quality warning, so they are now included
in the logs.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
@danxuliu
Copy link
Member Author

/backport to stable31

@danxuliu
Copy link
Member Author

/backport to stable30

@danxuliu
Copy link
Member Author

/backport to stable29

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

Successfully merging this pull request may close these issues.

1 participant