JSPM – @testrtc/watchrtc-sdk@1.27.2

Package Exports

@testrtc/watchrtc-sdk

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@testrtc/watchrtc-sdk) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

watchRTC offers users the ability to collect, track and analyze the metrics of real users on any WebRTC application.

This is done by including our watchRTC SDK which connects to the testRTC backend.

Installation

npm i @testrtc/watchrtc-sdk

Integration

Before any of your webrtc javascript code, add the following:

const watchRTC = require("@testrtc/watchrtc-sdk");
watchRTC.init();

This will transparently modify the RTCPeerConnection objects, allowing it to connect to the watchRTC backend service. The watchrtc parameter is needed to make this connection.

rtcApiKey - the watchRTC API key, as provided by testRTC
rtcRoomId - an identifier to the session/room/conference. This will enable an analysis of all participants in the same room as a single logical unit
rtcPeerId - an identifer of this peer/user in the session. This will make it easier to identify and troubleshoot users. It is recommended to use non-PII data here as much as possible
rtcTags - tags to associate with this peer connection. These can later be searched for or filtered

var pc = new RTCPeerConnection({
  ...,
  watchrtc:{
    rtcApiKey: "watchrtc api key",
    rtcRoomId: "identifier for the session"
    rtcPeerId: "identifier for the current peer",
    rtcTags: ["tag1", "tag2", "tag3"]
  }
});

Do not forget

For the operation of watchRTC, we have a websocket connected to our backend service for the duration of the session. Once you close the peer connection, you should also close our own websocket connection by calling

watchRTC.close();