Browse Source

Logs stream switch delays using analytics instead of callstats.

master
Boris Grozev 8 years ago
parent
commit
f4f0a7d90e
1 changed files with 7 additions and 8 deletions
  1. 7
    8
      conference.js

+ 7
- 8
conference.js View File

1305
 
1305
 
1306
         APP.UI.addListener(UIEvents.RESOLUTION_CHANGED,
1306
         APP.UI.addListener(UIEvents.RESOLUTION_CHANGED,
1307
             (id, oldResolution, newResolution, delay) => {
1307
             (id, oldResolution, newResolution, delay) => {
1308
-            var logObject = {
1309
-                id: "resolution_change",
1310
-                participant: id,
1311
-                oldValue: oldResolution,
1312
-                newValue: newResolution,
1313
-                delay: delay
1314
-                };
1315
-            room.sendApplicationLog(JSON.stringify(logObject));
1308
+                // We only care about the delay between simulcast streams.
1309
+                // Longer delays will be caused by something else and will just
1310
+                // poison the data.
1311
+                if (delay < 2000) {
1312
+                    JitsiMeetJS.analytics
1313
+                            .sendEvent('stream.switch.delay', delay);
1314
+                }
1316
         });
1315
         });
1317
 
1316
 
1318
         // Starts or stops the recording for the conference.
1317
         // Starts or stops the recording for the conference.

Loading…
Cancel
Save