fippo / rtcstats-server Goto Github PK

View Code? Open in Web Editor NEW

38.0 23.0 44.0 718 KB

Server for https://github.com/fippo/rtcstats

License: MIT License

JavaScript 98.22% Dockerfile 0.24% Makefile 0.19% HTML 1.35%

rtcstats-server's Introduction

rtcstats-server

server for https://github.com/opentok/rtcstats

Load errors

select starttime, colname, col_length, type, err_reason
    from stl_load_errors
    order by starttime desc;

views on recent data

create or replace view recent as select * from features_new order by date desc limit 100000;

Sample queries

The queries directory contains nodejs script that will connect to redshift, run a large number of queries and output a HTML file to stdout.

Extracting features from a local dump file

Move the dump file to the temp folder
Run node extract name-of-the-file

rtcstats-server's People

Contributors

Stargazers

Watchers

rtcstats-server's Issues

calculate delay between SLD/SRD

and SRD/addIceCandidate

setup instructions

are missing. Making a list here.

what is the primary key of the dynamodb table? 'Item'?
how is export to redshift done
what needs to be configured for passport?

investigate chrome metrics

things like https://www.chromestatus.com/metrics/feature/timeline/popularity/1042

receivingvideo10s is broken

https://github.com/opentok/rtcstats-server/blob/develop/features.js#L787-L808
-- this assumes a getStats frequency of once per second. Should instead measure the time.

retroactively run features

basically as follows:

select connection ids which don't have that feature in redshift
fetch data from s3
run feature
update dynamodb item

chrome 51 broke stuff

I was looking into the audiosendgoogrttmean feature and it has disappeared in Chrome >= 52. This is because https://bugs.chromium.org/p/webrtc/issues/detail?id=3377 has been fixed.

Those stats still appear but apparently not in the first report. For video this seems to be different?!
This means they're undefined and bad things happen in https://github.com/opentok/rtcstats-server/blob/develop/features.js#L1583-L1584

Solution is probably to filter undefined and then calculate instead of throwing away things if the first entry is undefined

Do not log IPs to make Antonio happy

detect higher-than-requested framerate

mostly linux bugs I think

minFrameWidth is -1

I saw a minGoogFrameHeightReceived of -1 -- that is bogus obviously and should be filtered.

positive/negative googEchoCancellationDelayMedia

seen it go from pos to neg. Does that mean there is echo?

scale it

the current model is to keep stuff in memory until the client closes the connection. That won't scale...

use presto?

https://prestodb.io/
when @baddn showed me this it seemed very similar to the current workflow. But better.

googAccelerateRate

https://code.google.com/p/chromium/codesearch#chromium/src/third_party/webrtc/media/base/mediachannel.h&q=accelerate_rate&sq=package:chromium&type=cs&l=646
fraction of data removed sounds bad. I just saw something 29%. Pretty sure this results in bad audio.
I want a mean, max, std dev of this

extract used audio/video codec

from getStats for Chrome, SDP for Firefox

needs a better plan for ssrc-stat extraction

extracting stats for a ssrc needs a better plan.

Basically:

extract local streams from addStream, remote streams from onaddstream
extract audio/video track
extract ssrc stats for track

"statsMeanRoundTripTime":null in Firefox

this is null in Firefox, causing issues with saving data

detect audio PLC kicking in

seems earlier than packet loss. googDecodingPLC

feature for frame(width/height) trashing

defined as max(number of framewidth changes per interval)

googrtt needs to be measured for the active connection

currently it is not

inconsistent internal use of .timestamp

sometimes its a unix timestamp, sometimes its a Date object.
The solution is probably to make .timestamp a unix timestamp everywhere and have .time as the equivalent date object.

dont obfuscate relay addresses in getStats

               "Cand-+zj+Zh1T" : {
                  "id" : "Cand-+zj+Zh1T",
                  "type" : "remotecandidate",
                  "portNumber" : 50144,
                  "priority" : 25108479,
                  "transport" : "udp",
                  "timestamp" : 1465744899781,
                  "candidateType" : "relayed",
                  "ipAddress" : "0.0.0.0"
               },

see #61 for why we don't need to obfuscate an ip we own.

detect all-zero jitter

to prevent things like http://logs.glob.uno/?c=mozilla%23media#c242496 :-(

crashes in zlib.js

the major remaining crash is in zlib.js line 623 which is this code:

      var newReq = self._handle.write(flushFlag,
                                      chunk,
                                      inOff,
                                      availInBefore,
                                      self._buffer,
                                      self._offset,
                                      self._chunkSize);

self._handle is null:

zlib.js:623
      var newReq = self._handle.write(flushFlag,
                               ^

TypeError: Cannot read property 'write' of null
    at Zlib.callback (zlib.js:623:32)

It is in the process that handles websockets so I suspect the websocket closes in the middle of things. Sounds like a bug in node-core...

infinity values

PC_0 FEATURE statsMeanReceivingBitrate => Infinity
PC_0 FEATURE statsMeanSendingBitrate => Infinity

ice restarts need consideration

I just saw a case where there was no remote relay candidate before the failure. There was one after the ice restart but that was counted as hadremoterelaycandidate => true which lead me to investigate this as "what the heck" instead of shrugging it off as "oh yeah, no remote relay. not gonna work"

Ability to start/end session outside opening/closing tab

We would love for there to be a way to start/end a session outside of opening and closing the tab. This is for example useful if you have a lot of back to back calls, and don't open a new browser window for every call. And if the user forgets to close the tab, we can end the session programatically and dump it to rtcstats at the logical end of the call, rather than closing the tab.

googCpuLimitedResolution + googBandwidthLimitedResolution percentage

i want a feature that calculates the percentage of googCpuLimitedResolution and googBandwidthLimitedResolution being true.

work with spec-stats

we're mostly relying on the google stats, we should be working with spec-stats more. One day...

determine whether the remote side is firefox or edge

by looking at the SDP. For Firefox this means looking for SDPARTA, for edge thisisadapterortc.

This will be helpful classifying ice failures.

extractTrack should not rely on onaddstream

https://github.com/opentok/rtcstats-server/blob/develop/features.js#L189-L220
relies on onaddstream. This caused a decrease in the number of records for some of our quality metrics.

Action:

fix this
shake fist at @henbos

detect micro-glitches

i've had a horrible call experience today (which turned out to be related to a broken battery and running low on that). Basically it glitched very, very often.

This is detectable in getStats. If packetsReceived or bytesReceived for a track stay the same despite a 1s difference in time that is a good indicator.

security: valid origins

how do we determine that a origin is authorized to send us data?

multistream handling

per discussion with @ggarber it is probably easiest to just make one row per stream/track

count number of ice failures and restarts

no gum calls or peerconnections made

this should be handled -- makes no sense to serialize something to the db then

write peerconnections to different files

currently, all data associated with a session is written to a single file. Splitting this up into one file for session metadata and another file for each peerconnection would allow processing a peerconnection once its done and not when the client closes the page.
Increases realtimeness and hopefully also reduces disk usage.

delta storage

getStats is currently stored as a full report. It would be much more efficient to store the same delta value that is transmitted.

changing dynamodb table names on the fly.

the size of our dynamodb table makes exports to redshift very hard. Also, we re-export the whole DB every time.

What we should do instead is to generate the tablename based on the current data. That assumes that the tables are created in advance but that is doable.

Tables can also be archived to S3 when they are no longer needed for read access.

WDYT @ggarber?

undefined in getstats

               "undefined" : "2016-06-03T20:45:52.297Z",

This oddly looks as if the timestamp is set wrong

number of different host candidates in onicecandidate

turn type used

we don't have a feature telling us what turn type is used. Basically a combination of the type pref code in https://github.com/opentok/rtcstats-server/blob/develop/features.js#L26 and the 'figure out connected pair' one in https://github.com/opentok/rtcstats-server/blob/develop/features.js#L1055

var maxmind = require('maxmind');

var cityLookup = maxmind.open('./GeoLite2-City.mmdb');
var city = cityLookup.get('2.150.33.235');
console.log(city.location);
console.log(city.country.iso_code);
console.log(city.continent.code);

which gives us location (lon/lat), county, continent and timezone

count googAdaptionChanges

they show bandwidth/cpu adaption. Lives on ssrc report currently

more ws woes

/home/ubuntu/rtcstats-server/node_modules/ws/lib/Receiver.js:386
    default: srcBuffer.copy(dstBuffer, dstOffset, 0, length); break;
                       ^

RangeError: out of range index
    at RangeError (native)
    at fastCopy (/home/ubuntu/rtcstats-server/node_modules/ws/lib/Receiver.js:386:24)
    at Receiver.add (/home/ubuntu/rtcstats-server/node_modules/ws/lib/Receiver.js:86:3)
    at Socket.realHandler (/home/ubuntu/rtcstats-server/node_modules/ws/lib/WebSocket.js:800:20)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:177:18)
    at Socket.Readable.push (_stream_readable.js:135:10)
    at TCP.onread (net.js:542:20)

seems to be websockets/ws#778 even though that is using ws 1.x whereas we are still stuck on 0.8