Working with SRT statistics
On this page, you will find documentation on working with live stream statistics using the SRT protocol. For production ingest and monitoring, see continuous streaming. For playback integration and analytics, use video api. Recommended product path: Ingest & route, Player & embed. For this workflow, Player & embed is the most direct fit., and scaling guide. For this workflow, Paywall & access is the most direct fit.
Callaba SRT Statistics provides a wide range of real-time data about the network node. This data can be used to monitor the state of the live stream and track any erroneous behavior.
This module in Callaba is implemented using Data Streaming messages, a real-time data processing approach. It differs from traditional batch processing, where data is collected, stored, and processed in batches. In streaming processing, data is continuously processed as it arrives.
To obtain statistical data about your SRT streams, you can establish a connection via WebSocket:
SRT active streams and event log live demo
To view a code example for receiving messages via WebSocket, open any of the examples listed above in your IDE.
Types of data stream messages
There are two types of messages you can subscribe to in order to receive up-to-date statistics.
- MODULE_SRT_SERVERS_STATS
Use this message to get statistical data about your live streams. This is especially useful when you need to monitor anomalies such as bitrate or round-trip delay during the broadcast.
See code example - MODULE_SRT_SERVERS_ACTIVE_STREAMS
Use this message to get active working streams as well as a timeline of stream connection or disconnection events. This is especially useful for monitoring the current state of the pipeline and tracking reconnection anomalies.
See code example
Getting SRT Statistics live demo
For more details on each statistical property, you can refer to the SRT protocol documentation at the provided link.
SRT socket statistics docs by Haivision
Getting SRT active streams and event log live demo