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

Not correct statistics #1819

Open
woogeunshin opened this issue Feb 24, 2022 · 5 comments
Open

Not correct statistics #1819

woogeunshin opened this issue Feb 24, 2022 · 5 comments

Comments

@woogeunshin
Copy link

I added this configuration in the .env file to enable statistics.
DOLIBRI_REST_ENABLED=true

And add this ports under "jvb" in the docker-compose.yml
ports:
- '${JVB_PORT}:${JVB_PORT}/udp'
- '${JVB_TCP_PORT}:${JVB_TCP_PORT}'
- '8080:8080'

After that, I could see the statistics through this address.
https://localhost:8080/colibri/stats

The statistics looks good until I generate packet loss and add delay between video packets.
I made 10% packet loss for the Video packet.
But any loss count did not increase, even though several keys are there about loss.
"overall_loss" : 0.0
"incoming_loss" : 0.0
And I added the delay between video packets several hundreds of milliseconds.
But the round trip time did not change, compare to no insertion delay.
"rtt_aggregate":6.85408"

I could confirm packet loss and insertion delay through video quality and response time.
The response time increases and video quality is poor.
And also, the statistics in the remote video windows show increasing E2E delay and packet loss.
It is showing only when the mouse pointer placed on the antenna UI in the remote video window.

Other statistics are showing well, like "conferences", "participants".
Could you know why the loss and RTT do not reflect real value?

@damencho
Copy link
Member

Please, when you have questions or problems use the community forum before opening new issues, thank you.

@damencho damencho transferred this issue from jitsi/docker-jitsi-meet Feb 24, 2022
@bgrozev
Copy link
Member

bgrozev commented Feb 24, 2022

The only thing that comes to mind is that your endpoints are connected p2p. You can see much more detailed stats using http://localhost:8080/debug?full=true (it's a lot of data). Look for endpointConnectionStats for individual endpoints' RTT and loss.

@woogeunshin
Copy link
Author

Sorry, I will use community forum later.
I understood this case. I couldn't see the p2p connection statistics like loss and RTT in the server side.
And I've tried http://localhost:8080/debug?full=true.
It shows several statistics. But, there is no endpointConnectionStats.
{"shutdownInProgress":false,"time":1645671085302,"load-management":{"state":"NOT_OVERLOADED","stress":"0.0","reducer_enabled":"false","reducer":{"jvbLastN":-1}},"overall_bridge_jitter":null,"conferences":{},"health":"OK"}

Did I miss something?

@bgrozev
Copy link
Member

bgrozev commented Feb 24, 2022

This means there were no active conferences at the time you made the request: "conferences":{}

@woogeunshin
Copy link
Author

Thank you, @bgrozev.
I could take statistics using http://localhost:8080/debug?full=true.
I could identify streams with SSRC number. But, It's not easy to know where they come before Ethernet packet capture.
I think that the IP address is more familiar than SSRC number.
Is it possible adding IP address in the debug file?

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