Streaming Media Device

How to Create Devices and Targets

• • Creating a Device
  • Adding Several Targets within a Single Device

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).

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

The task execution involves the following steps:

1. The system hits the stream URL and connects 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 the 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 Target

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, “https://streammedia.com/stream.asf”.

Time Validation Threshold (in seconds)

This setting specifies the maximum time, in seconds, that the system will wait for a response from the target resource. If the response is not received within the defined time, the system flags it as an error.

Prepare Script

Apart from the media URL, you can choose MediaEngine and ReportDetails by adding to the Prepare Script field:

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

(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  = ( “GENERAL”, “WMP”)

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

Error Filter

You can create filters to ignore specific errors that may occur but are not relevant to the purpose of a particular device. When an error matches a configured filter, the system will not generate alerts for that response. For example, DNS-related errors can be ignored if DNS server availability is managed by a third party.

Tips

• To ignore a range of error codes, use a dash (for example, 500–504).
• To ignore several error codes in a specific category, list the codes separated by commas or semicolons (for example, 404;504).

You can find a comprehensive list of supported error codes in the HTTP Status Codes List | HTTP Error Codes Explained article of this wiki.

For example, if 404 errors are expected or not relevant for a specific device, you can filter them out to avoid receiving alerts when those errors occur. The error details will still be available for review in the device reports.