Streaming Media Monitoring checks video and audio streaming services for performance, errors, and availability.

The monitoring agent connects to the media server, performs buffering, and plays the stream for 30 seconds. Then, the monitoring agent disconnects.

The monitoring agent will check for errors and also measures metrics, including: Connection Time, Buffering Time, Received Packages, Buffering Packages, Frame Rate and Average Bytes Per Second

Descriptions of these metrics:

Connection – time value measured between sending the first request and getting first frame of media stream.

Duration – time when media source was in process. Depending on method used by streaming server (streaming vs. progressive download) duration may reflect download of sufficient part of file for further analysis or time engine spent on capturing stream.

FPS – the ratio of all frames that we downloaded from the given stream to the total time of monitoring (connection + stream playback).

FPS = all downloaded frames / monitoring time

Quality – reflects estimated streaming performance or in other words visual quality of streams. It represents the ratio of actual FPS while playing sample part to the original properties specified in a stream.  In response Description engine type is always displayed.

General. Underlying codecs of this engine return quality value themselves. This engine has peculiarity – it counts only video streams correctly. Clean audio stream will show 0 quality  value.

  • Real-life example explaining this peculiarity

WMP (Windows Media Player) – quality is being calculated by formula Q = actual FPS / specified FPS

Flash – quality is being calculated by formula Q = actual FPS / specified FPS

Silverlight – quality is being calculated by formula Q = actual FPS / specified FPS



Supported protocols: applehttp, concat, crypto, file, gopher, hls, http, httpproxy, mms, pipe, rtmp, rtp, tcp, udp, rtsp, https.