Ultra-Low Latency Streaming With Full Operational Visibility
Ultra low-latency streaming has become business-as-usual for live streaming operators, particularly for sports betting, as they offer interactive features and even wagering within their platforms. The WebRTC protocol is the preferred method for real-time streaming, and companies like Dolby.io, Phenix Real Time Solutions, and Red5 offer WebRTC-based services and solutions. The challenge is that WebRTC isn’t as easy to monitor as HTTP, as it involves monitoring stats that sit outside the video player API. And further, streaming operators still want the ability to capture and correlate viewership data and QoE data from the video player API. Without the operational management and insight to those real-time streams, there’s no way to monitor performance, and ensure a high QoE expected by viewers.
Datazoom's platform has been proven to help broadcasters and OTT publishers improve WebRTC monitoring to ensure the best QoE and QoS for real-time streams.
Can You Afford To Blindly Stream in Real-Time?
When WebRTC became a streaming option, live streaming providers jumped on the bandwagon. For the first time, they could provide truly real-time experiences for sporting, company town halls, and other events. Combined with interactive features, like chatting for users or fans, WebRTC has the potential to offer a consistent, broadcast-like streaming experience that everyone is accustomed to.
But streaming can be less reliable than broadcast, and a protocol like WebRTC can be even more challenging. Without the operational insight to report, diagnose, and fix errors, ultra-low latency streaming is challenging, and can come at a cost. What’s required is the ability to capture player data about the stream, to trace it back up through the workflow, and identify disruptions in the experience so they don’t go undetected and result in significant impact to subscriber satisfaction.
Maximize Betting Revenue
For many sports betting providers using WebRTC, the protocol offers the ability to support interactive experiences, such as wagering, which require real-time streaming. So when there is a service disruption, such as additional latency or a corruption of chunks, it can cause viewers to miss or lose bets. Datazoom enables providers to maximizing the ‘purse’ on an event through helping to ensure the latency is as low as possible to keep the betting window as long as possible, and ensuring the stream quality doesn’t cause user churn.
Ensure The Best Real-Time QoE
Viewers are driven by the quality of the service, not just the type of content. So when they subscribe to a streaming service that promises real-time experiences, the expectation is that those streams are of equal quality to others services. WebRTC monitoring from Datazoom can be combined with other datasets to create observability to reduce time to resolution (TTR) and even identify, diagnose, and resolve developing quality issues before they impact the ‘purse’ on an event.
Enable Holistic Monitoring
Streaming operators who employ WebRTC to enable different experiences often have to develop parallel monitoring workflows and sometimes a fail-over technology stack. This can complicate the monitoring process by making it more difficult to see a holistic picture of QoE, especially for viewers who might be switching between real-time and standard streaming. With Datazoom’s WebRTC monitoring, data for the real-time protocol can be delivered in the same data stream as viewer data for other protocols and delivered to a unified dashboard.
Through the Datazoom DaaS Platform, live streaming operations can effectively monitor WebRTC streams to protect and optimize use cases like real-time betting.
How WebRTC Monitoring Can Be Addressed Using the Datazoom DaaS Platform
Datazoom’s HTML5 Collector can be used to collect directly from the WebRTC stats API. Using Datazoom, we create a ‘WebRTC Heartbeat” event with event specific metadata in order to report on the connection health. The WebRTC frequency can be set within the Datazoom platform UI (collector configuration).