Integration with watchRTC

watchRTC comes with a rich and powerful set of integration features. These are meant to make sure you can enrich the data stored in watchRTC, export it to your system and make use of it in ways that are suitable for your needs.

  • Connecting to watchRTC

    The watchRTC SDK automatically connects to the watchRTC servers when a peer connection is created in your web application. Sometimes, application developers would rather connect earlier than that. This has the added...

  • Using custom keys in watchRTC

    When you connect a session with watchRTC, you provide a roomId and a peerId. Oftentimes, this isn’t enough to offer the context you need. To compensate for that, watchRTC includes...

  • Adding custom events in watchRTC

    Your application has its own set internal logic that is outside the scope and context of WebRTC itself. As such, the watchRTC SDK cannot be aware of these events and track them on its own. In or...

  • Console logs in watchRTC

    The watchRTC SDK can also collect browser console logs. While these might be verbose, they can be quite useful to trace and resolve application related issues. Note: The ability to collect con...

  • Mapping streams in watchRTC

    Media channels in watchRTC are labeled based on the names assigned to them by WebRTC, which usually revolves around the SSRC of the streams. In group sessions this can make figuring out which channel is coming from whi...

  • Webhook support in watchRTC

    watchRTC offers the ability to set up custom alerts. You can use webhooks in order to catch these custom alerts in your application or external monitoring service. Setting up webhooks in watchRTC Navigate to Settings s...

  • Setting up custom alerts in watchRTC

    You can setup your own custom alerts in watchRTC. This enables you to identify and troubleshoot connectivity and media quality issues faster. What are custom alerts? watchRTC has a mechanism called alerts. With this me...

  • Deep linking to rooms and peers

    Oftentimes, you will have your own metadata associated with the rooms and peers you store in watchRTC. You might even have dedicated URLs for them, linking towards your database dashboard or other monitoring systems...

  • Setting up a proxy for watchRTC traffic

    watchRTC uses a websocket connection from the users to our servers in order to collect the WebRTC statistics and telemetry data necessary for monitoring your service. At times, you may want to use an intermediary proxy whi...

  • Persistent connections and watchRTC

    Some contact centers use the same WebRTC peer connection for multiple calls. This is done in order to reduce the call setup time by having the connection persist. It makes sense when call center agents are “on the p...

  • Data Streams in watchRTC

    Data streams in watchRTC are generated on the room level. Once a data stream file needs to be created for watchRTC, watchRTC will collect all history results for the time interval configured and generate a JSON stru...

  • Collection Intervals in watchRTC

    Collection Intervals refer to how frequently data is sampled when gathering statistics. You can choose any duration between 1 and 300 seconds (equivalent to five minutes). It determines the waiting time between data...

  • How to embed watchRTC information in web pages

    You can now take the room and peer pages from the watchRTC History and embed them as an iframe component in your own web pages. Read on to learn more. Why is this useful? This is useful when you want to share such info...

  • Handling long duration sessions [8+ hour]

    8 hours has been found to be the optimal time for a longer duration session. Anything longer should be handled differently, using the API to instruct connections and disconnects after the 8-hour mark. Keep read...

  • Track Identifiers

    Track identifiers in the context of WebRTC (Web Real-Time Communication) are unique identifiers assigned to audio and video tracks. They are used to distinguish individual tracks within a media stream. These id...