How to create devices and tasks

Streaming media monitoring checks video and audio streaming services for performance, errors, and availability.

Identify the Media You Are Trying to Monitor

This is frequently confused with the web page or media player location on your website.  The target of a streaming media task will not be the URL of a player or webpage that contains the player, but the  actual media resource path that is used by a player to play the file.

Once you have identified the location, check the media file type. What protocol does it use? (make sure to specify the protocol in the file path (such as rtmp:// or https://, for example).

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

Depending on the file type and codec, the task will play back the media file in one of several engines which generate slightly different monitoring values: a general player, Windows Flash Player.

The task execution involves the following steps:

  1. The system hit the stream URL and connect the stream server.
  2. In the case of the playlist, the system gets the list of the stream URLs.
  3. The stream properties such as codec, quality, etc. are requested from the server.
  4. The system downloads first 30 sec of the stream to decode.
  5. If the source server is unavailable or the system failed to download the 30 sec of stream playback, the error will be generated.

Creating a task

Once you have created a device and are adding or editing a task, you will be prompted to adjust the following settings.

Stream URI

Enter the address of the actual media source you wish to monitor. Note that the URL must link directly to the media file and not a web page that contains a media player. For example, http://streammedia.com/stream.asf

Completion Timeout (in seconds)

Enter the number of seconds the task should wait for a response from the web page before ending the task and returning an error. If this is left blank the default timeout for a task is 120 seconds.

Custom Script

Apart from media URL you can choose MediaEngine and ReportDetails by adding into the Custom Script field:

(Tasks[0] as Media).MediaEngine= “SMOOTH”;

(Tasks[0] as Media).ReportDetails = “FULL”;

Where,

Tasks[<sequential number of the task>] – specifies the sequential number of the task in the device. Note that the numbering of tasks in the device starts from 0. So to refer to the first task in the device you should provide Tasks[0].

MediaEngine  = ( “FLASH”, “GENERAL”, “SMOOTH”, “WMP”, “FLASH_FC”)

ReportDetails = (“STANDART”, “FULL”, “SHORT”)

In case of “FLASH_FC” engine should contain required MediaHost and MediaStream.

Example:

(Tasks[0] as Media).MediaHost = "rtmp://fml.126F2.alphacdn.net/20126F2/MediaPlayer/";    
(Tasks[0] as Media).MediaStream = "simulcast-flash-128k";
(Tasks[0] as Media).MediaEngine= " FLASH_FC";
(Tasks[0] as Media).ReportDetails = "Full";