24ae746a88
Jitter evaluation, as an alert trigger, was changed in 3.0 to get the internal average jitter used in the conn-status component data (which is total jitter delay divided by jitterbuffer emit events). This was done accidentally and that metric is _very_ different from the one used in 2.7 (point-in-time jitter from remote-inbound-rtp/inbound-rtp, highest on the interval, gathered on /utils/stats.js). The alert thresholds were preserved, which makes it overly sensitive in regards to jitter (and thus causes it to be critical whenever the user is in audio). Remove jitter as a connection status alert trigger, which fixes the false positive. The implementation on <= 2.7 is also not ideal - if anything, it generates false negatives. That's why I'm removing jitter for the time being since it's ill-suited (at least in the way it's used) for what we want to achieve. |
||
|---|---|---|
| .. | ||
| .meteor | ||
| .vscode | ||
| client | ||
| imports | ||
| private/config | ||
| public | ||
| server | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| deploy_to_usr_share.sh | ||
| footer | ||
| jsconfig.json | ||
| meteorless.sh | ||
| package-lock.json | ||
| package.json | ||
| run-dev.sh | ||
| test-html5.sh | ||
| tsconfig.json | ||