Skip to main content
You can access call logs and metrics for every call to help you better understand your calls and troubleshoot issues as they arise. Call logs characterize what happens on a call from the point of view of each participant. These logs include information about resource bundle downloads, signaling connections, peer-to-peer & SFU call connections and events, and participants’ environments, actions, and error states. Call metrics help to assess the performance and stability of the connection by providing transport layer, candidate-pair, and track level statistics. Data starts being collected by the browser client once a second participant joins a call. The first data sample is logged after 15 seconds. Subsequent samples are logged every 15 seconds.

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.
  • limit defaults to 20, too small to reach them. Raise it (maximum 1000).
  • Do not set logLevel. The network type line is a debug log, so info or error drops it.