Streaming Tab

Path: Monitoring > Streaming

Figure 165

The Streaming Media tab shows streaming media usage on the appliance. It can be used to monitor usage, verify that bandwidth limits are set appropriately, and determine what percentage of bytes are being delivered from cache.

Streaming RTSP Statistics

RTSP Server Statistics

Connections from Player to Cache: These statistics are for the RTSP/RTP connections from clients (players) to the appliance. If QuickTime HTTP Tunnel Caching is enabled on the Streaming Tab, HTTP tunneled statistics are included.

• Peak: The peak number of active connections from players.
• Active: The current number of active connections from players.
• Total: The total number of connections from players since the appliance was started.

Total Requests: The total number of player requests received since the appliance was started.

Active Bandwidth (Kbps): The downstream bandwidth currently being used.

RTSP Client Statistics

Connections from Cache to Origin Server: These statistics are for the RTSP/RTP connections from the appliance to the origin streaming servers.

NOTE:  The appliance fills audio and video tracks separately, so a single connection from a player will often result in two (and sometimes more) connections to the origin streaming server.

• Peak: The peak number of active connections to origin streaming servers.
• Active: The current number of active connections to origin streaming servers.
• Total: The total number of connections to origin servers since the appliance was started.

Total Requests: The total number of appliance requests to origin streaming servers since the appliance was started.

Active Bandwidth (Kbps): The upstream bandwidth currently being used.

General RTSP Statistics

Number of Bytes: The total number of streaming bytes processed by the appliance traffic since it was started.

• Sent to Player: The total number of bytes sent to players since the appliance was started.
• Filled from Origin: The total number of bytes filled from origin servers since the appliance was started.

CPU Utilization: The system CPU utilization.

Byte Hit Rate: The percentage of bytes which were already in cache when requested. This is more meaningful than overall hit rate, because streaming objects can be very large and might be partially cached.

Total Errors: The total number of errors since the appliance was started.

Total ACL Rejections: The total number of connections rejected due to IP ACL controls since the appliance was started.

Not Modified Replies: The total number of not-modified messages since the appliance was started.

Total Streams Served: The total number of streams served since the appliance was started.

HTTP Tunneling Statistics (Pass Through Only)

These statistics reflect content which passes uncached through the appliance.

This occurs under the following conditions:

• The QuickTime HTTP Tunnel Enable checkbox is not checked.
• A compatible MediaCache service is not available to cache the content.

HTTP Tunneling Server Statistics

Total Connections: Total number of HTTP tunneling pass-through connections from players since boot time.

HTTP Tunneling Client Statistics

Total Connections: Total number of HTTP tunneling pass-through connections to origin servers since boot time.

General HTTP Tunneling Statistics

Number of Bytes: The total number of bytes that have passed through the appliance since it was started.

• Sent to Player: The total number of bytes sent to players using HTTP tunneling pass-through mode since the appliance was started.
• Filled from Origin: Total number of bytes received from origin streaming servers using HTTP tunneling pass-through mode since the appliance was started.

CPU Utilization: System CPU utilization.

Byte Hit Rate: This will always be zero because HTTP tunneling pass-through content is never cached.