Questions about quality and telemetry

Leonid_Leontiev · February 16, 2023, 10:31pm

I have questions about getting statistics on video quality:

Is it possible to determine the reason why the quality drops from Q3 to Q1 (320*180) ?
How does JVB measure the quality of the channel to the client? Can it be predicted?
Project GitHub - jitsi/rtcstats uses data from the client. Is there a similar project with JVB metrics? I found GitHub - engesin/Jitsi-Prometheus-Exporter: Jitsi Prometheus Exporter (JPE) but here generalized statistics are used, but I would like to see a conference-participant-stream-track metrics. Is it possible to get it?
Is it possible to determine which headset-camera is used? Some users experience issues with certain brands.

saghul · February 17, 2023, 9:23pm

I don’t think we have stats for that.

It estimates the bandwidth and backs down if packet loss is perceived (this is an oversimplification).

I don’t think we feed rtcstats from the JVB.

I think the current device is something which is sent to rtcstats.

damencho · February 17, 2023, 10:03pm

We do actually. GitHub - jitsi/jvb-rtcstats-push

Leonid_Leontiev · February 18, 2023, 4:18pm

Is it possible to get statistics on user-agents - what client-version(browser or mobile) do users use?

damencho · February 18, 2023, 5:27pm

You can do that with enabling amplitude integration.

github.com

jitsi/jitsi-meet/blob/00ed794c50b24a909b965c1e597687fd8b8b820b/config.js#L962


      
          // disabled: false,
          
          
// The Google Analytics Tracking ID:
          // googleAnalyticsTrackingId: 'your-tracking-id-UA-123456-1',
          
          
// Matomo configuration:
          // matomoEndpoint: 'https://your-matomo-endpoint/',
          // matomoSiteID: '42',
          
          
// The Amplitude APP Key:
          // amplitudeAPPKey: '<APP_KEY>',
          
          
// Obfuscates room name sent to analytics (amplitude, rtcstats)
          // Default value is false.
          // obfuscateRoomName: false,
          
          
// Configuration for the rtcstats server:
          // By enabling rtcstats server every time a conference is joined the rtcstats
          // module connects to the provided rtcstatsEndpoint and sends statistics regarding
          // PeerConnection states along with getStats metrics polled at the specified
          // interval.

Or writing your own analytics implementation, adding that and handling it in your choice of backend.

github.com

jitsi/jitsi-meet/blob/00ed794c50b24a909b965c1e597687fd8b8b820b/config.js#L991


      
              // will only send data related to RTCPeerConnection events.
              // rtcstatsPollInterval: 10000,
          
          
    // This determines if rtcstats sends the SDP to the rtcstats server or replaces
              // all SDPs with an empty string instead.
              // rtcstatsSendSdp: false,
          
          
    // Array of script URLs to load as lib-jitsi-meet "analytics handlers".
              // scriptURLs: [
              //      "libs/analytics-ga.min.js", // google-analytics
              //      "https://example.com/my-custom-analytics.js",
              // ],
          },
          
          
// Logs that should go be passed through the 'log' event if a handler is defined for it
          // apiLogLevels: ['warn', 'log', 'error', 'info', 'debug'],
          
          
// Information about the jitsi-meet instance we are connecting to, including
          // the user region as seen by the server.
          // deploymentInfo: {
          //     shard: "shard1",