Real-time monitoring

Real-time monitoring provides end-to-end visibility into your live streaming pipeline. You can monitor at both the stream and domain name levels to quickly identify quality fluctuations and diagnose issues.

Usage notes

Data granularity ranges from 5 seconds to 1 minute, depending on the metric. This differs from the intervals used in operational analysis and usage queries, so data for the same time period may not match. Billing is based on usage query data.
The maximum query time range and data availability vary by metric. See the tables below for details.

Query data

Log on to the ApsaraVideo Live console.
In the left-side navigation pane, choose Live Center > Monitoring > Real-time Monitoring.
View the real-time monitoring details.

Stream data

Enter a stream ID to query per-stream metrics, including ingest data, playback data, live center stream quality, stream records, and callback records.

For an original stream, enter the exact StreamName.
For a transcoded stream, enter StreamName_TranscodingTemplateID.

Category	Metric	Limits
Stream Ingest Statistics	Ingest traffic, ingest bandwidth, video frame rate, video bitrate, audio frame rate, audio bitrate, and client IP address for a single stream. If the same IP address re-ingests a stream, the new session is shown as a separate curve in a different color. Note Ingest data reflects the stream quality measured at the edge nodes.	The maximum time range for a single query is 3 hours. You can query only data from the last 30 days.
Playback Statistics	Playback bandwidth, playback traffic, online users (concurrent connections), and new connections for a single stream. The online users (concurrent connections) metric represents the number of viewers currently watching the live stream, covering connections from both mobile and desktop devices. New connections cannot be queried for HTTP Live Streaming (HLS). Concurrent HLS connections are counted only for requests that match the default URL format: M3U8 request: `http(s)://example.aliyundoc.com/Appname/StreamName.m3u8` TS segment request: `http(s)://example.aliyundoc.com/Appname/StreamName/153*****_137*.ts` To count connections for non-default URL formats, submit a ticket to request custom configuration.	The maximum time range for a single query is 24 hours. You can query only data from the last 30 days.
Live Center Stream Quality	Stream quality data from the live center, including video and audio frame rates and bitrates.	The maximum time range for a single query is 3 hours. You can query only data from the last 30 days.
Live Streaming Records	Domain name, AppName, StreamName, ingest start and end times, client IP address, and transcoding template ID for each stream session.	The maximum time range for a single query is 30 days. You can query only data from the last 30 days.
Callback Records	Callback event records for a single stream, including ingest start/stop, recording, and exception events. Each record shows the callback URL, trigger time, callback content, and HTTP request status.	The maximum time range for a single query is 20 days. You can query up to 1,000 callback records from the last 20 days.

Domain name data

Category	Metric	Limits
Playback Statistics	Playback traffic, playback bandwidth, HTTP status code count, and HTTP status code distribution at the domain level.	The maximum time range for a single query is 24 hours. You can query only data from the last 7 days.
Stream Ingest Statistics	Ingest traffic, ingest bandwidth, HTTP status code count, and HTTP status code distribution at the domain level.	The maximum time range for a single query is 1 hour. You can query only data from the last 7 days.

FAQ

What do I do if real-time monitoring API queries return no data or the results are inconsistent with console data?

Check the following common causes:

Data delay: Monitoring data from API interfaces is subject to a certain processing and propagation delay. If you cannot query recent data, query historical data from yesterday or within the last 31 days to verify if the API can return data properly.
Incorrect time format: APIs such as DescribeLiveStreamPushMetricDetailData require start and end times in UTC format (for example, 2026-05-17T16:00:00Z). However, the console typically displays data in your local time zone by default. You must convert your local time to UTC before making the API call.