bigbluebutton-Github/bigbluebutton-html5/imports/utils/stats.js

194 lines
4.2 KiB
JavaScript
Raw Normal View History

import logger from '/imports/startup/client/logger';
// Probes done in an interval
const PROBES = 5;
2019-11-30 19:29:51 +08:00
const stop = callback => {
2020-01-30 01:52:55 +08:00
logger.debug(
{ logCode: 'stats_stop_monitor' },
2019-11-30 19:29:51 +08:00
'Lost peer connection. Stopping monitor'
);
callback(clearResult());
return;
};
const isActive = conn => {
let active = false;
if (conn) {
const { connectionState } = conn;
const logCode = 'stats_connection_state';
switch (connectionState) {
case 'new':
case 'connecting':
case 'connected':
case 'disconnected':
active = true;
break;
case 'failed':
case 'closed':
default:
logger.warn({ logCode }, connectionState);
}
} else {
logger.error(
{ logCode: 'stats_missing_connection' },
'Missing connection'
);
}
return active;
2020-02-15 05:14:21 +08:00
};
const collect = (conn, callback) => {
const INTERVAL = window.meetingClientSettings.public.stats.interval / PROBES;
let stats = [];
const monitor = (conn, stats) => {
if (!isActive(conn)) return stop(callback);
conn.getStats().then(results => {
2019-11-30 19:29:51 +08:00
if (!results) return stop(callback);
let inboundRTP;
let remoteInboundRTP;
results.forEach(res => {
switch (res.type) {
case 'inbound-rtp':
inboundRTP = res;
break;
case 'remote-inbound-rtp':
remoteInboundRTP = res;
break;
default:
}
});
if (inboundRTP || remoteInboundRTP) {
if (!inboundRTP) {
2020-01-30 01:52:55 +08:00
logger.debug(
{ logCode: 'stats_missing_inbound_rtc' },
'Missing local inbound RTC. Using remote instead'
);
}
stats.push(buildData(inboundRTP || remoteInboundRTP));
while (stats.length > PROBES) stats.shift();
const interval = calculateInterval(stats);
callback(buildResult(interval));
}
setTimeout(monitor, INTERVAL, conn, stats);
2020-01-30 01:52:55 +08:00
}).catch(error => {
logger.debug(
{
logCode: 'stats_get_stats_error',
extraInfo: { error }
},
'WebRTC stats not available'
);
});
};
monitor(conn, stats);
};
const buildData = inboundRTP => {
return {
packets: {
received: inboundRTP.packetsReceived,
lost: inboundRTP.packetsLost
},
bytes: {
received: inboundRTP.bytesReceived
},
jitter: inboundRTP.jitter
};
};
const buildResult = (interval) => {
const rate = calculateRate(interval.packets);
return {
packets: {
received: interval.packets.received,
lost: interval.packets.lost
},
bytes: {
received: interval.bytes.received
},
jitter: interval.jitter,
rate: rate,
loss: calculateLoss(rate),
MOS: calculateMOS(rate)
};
};
const clearResult = () => {
2019-11-30 19:29:51 +08:00
return {
packets: {
received: 0,
lost: 0
},
bytes: {
received: 0
},
jitter: 0,
rate: 0,
loss: 0,
MOS: 0
};
};
const diff = (single, first, last) => Math.abs((single ? 0 : last) - first);
const calculateInterval = (stats) => {
const single = stats.length === 1;
const first = stats[0];
const last = stats[stats.length - 1];
return {
packets: {
received: diff(single, first.packets.received, last.packets.received),
lost: diff(single, first.packets.lost, last.packets.lost)
},
bytes: {
received: diff(single, first.bytes.received, last.bytes.received)
},
jitter: Math.max.apply(Math, stats.map(s => s.jitter))
};
};
const calculateRate = (packets) => {
const { received, lost } = packets;
const rate = (received > 0) ? ((received - lost) / received) * 100 : 100;
if (rate < 0 || rate > 100) return 100;
return rate;
};
const calculateLoss = (rate) => {
return 1 - (rate / 100);
};
const calculateMOS = (rate) => {
return 1 + (0.035) * rate + (0.000007) * rate * (rate - 60) * (100 - rate);
};
2020-01-30 01:52:55 +08:00
const monitorAudioConnection = conn => {
if (!conn) return;
logger.debug(
{ logCode: 'stats_audio_monitor' },
'Starting to monitor audio connection'
);
collect(conn, (result) => {
const event = new CustomEvent('audiostats', { detail: result });
window.dispatchEvent(event);
});
};
export {
monitorAudioConnection,
refactor(connection status): remove legacy monitor Remove parts of a previous connection monitor. To add some context (as far as my memory goes) to the multiple connection monitor features the product has, `stats` (currently named `connection status`) was introduced at the Flash client back in ~2016. @fcecagno and I did it as a BigBlueButton's Summit activity. Our work was squashed into a single commit in 92554f8b3e39918a88af0ae9f5b85057cb0556eb :). I'm not sure about the whole story behind `network information` (the late connection monitor added to the HTML5 client) but I assume it should work as a collector for a bunch of different connectivity monitors. I remember when it was introduced but I don't know why it wasn't adopted. My best guess would be because of some performance issues the `user list` had back then. To follow on why `connection status` replaced `network information` at the HTML5 client, when I did the `multiple webcams` feature I had to refactor a big chunk of the `video provider` (#8374). Something that wasn't really helping there was the adaptation of `stats` that was made to show local feedback for each webcam connection. Although this feature wasn't being used anymore, `network information` did rely on that to build up data. With this monitor gone I assumed it was my responsibility to provide an alternative so I promoted Mconf's port of the Flash `stats` monitor to BigBlueButton's HTML5 client (#8579). Well, that's my perspective on how things went for those features. If anyone would like to correct me on something or add something else on that history I would appreciate to know.
2021-06-13 23:36:43 +08:00
};