Accessing information
Call logs and metrics are made available through the Daily Dashboard and the/logs endpoint.
Additionally, we’ve built a sample app — Daily Call Explorer — as an example of how this information can be used.
Finding a participant’s browser, OS, and network type
Each/logs row has time, clientTime, message, mtgSessionId,
userSessionId, peerId, domainName, level, and code. Browser, OS,
device type, and network type are not fields of their own. They sit in the text
of message. The Daily Dashboard reads them the same way.
The value is everything after the first
=.
OS =: split on the first space. The first word is the name; the rest is the
version. Some clients report a multi-word version (for example
OS = Windows 10 Win 10), so keep the whole remainder.
Network type: this one is not a key = value line. It looks like
using sfu-send networkType: wifi. Match any message that contains
networkType:, take the text after : , and drop anything from / on. The
value comes from the browser’s WebRTC stats (wifi, ethernet, cellular).
Not every browser reports it, so the line can be missing. It can also appear
more than once, and the value changes if the participant switches networks.
One value for web and native clients: read Library when present, else
Browser. Do the same for LibraryVersion and BrowserVersion.
Query: these lines are logged once, early in a participant’s session, so ask
for that participant’s logs in ascending order:
- They do not land at a fixed row. A client logs setup detail first, so scan the rows for the prefixes instead of reading a set number off the top.
limitdefaults to20, too small to reach them. Raise it (maximum1000).- Do not set
logLevel. The network type line is a debug log, soinfoorerrordrops it.