HDN1 Live Streaming traffic reports

The HDN1 Live Streaming traffic report contains the following information:

  • Concurrent Streams. The maximum and overall average concurrent streams, per five-minute period, for the selected time period. You can view a graph for concurrent streams By Average and By Max by clicking the appropriate tab.
    • By Average. This graph shows the average number of concurrent streams for each five minute period. It shows the average number of concurrent streams over the time period selected and the latest recorded number of concurrent streams.
    • By Max. This graph shows the maximum number of concurrent streams for each five minute period. It shows the peak number of concurrent streams over the time period selected and the latest recorded number of concurrent streams.

      The maximum number of streams for each five minute period is probably higher than the average, so the maximum for the entire period might be higher than the peak points on the graph.

  • Edge Bandwidth, in Mbits per Second. The total bandwidth, peak bandwidth, and total volume for the CP code(s) and time period selected. This data includes the following:
    • Request traffic. Includes the Request HTTP header size and any protocol overhead.
    • Response traffic. Includes object bytes plus overhead bytes.
      • Origin traffic, including all HTTP response codes.
      • Midgress traffic, including all HTTP response codes. Midgress bandwidth is counted twice, once when the response is sent by an Edge server, and the second time when it is received.
      • Edge traffic, including all HTTP response codes.
        Note: Tiered Distribution midgress bits—bits served from the Tiered Distribution infrastructure to Edge servers—are counted as Edge bits in real-time data. There is currently no way to segment Tiered Distribution midgress bits from Edge bits in real-time data.
  • Edge Traffic, in Hits per Second. The total number of hits for the selected CP code(s) and time period. The peak number of hits per second and the total hits are highlighted in the graph. The breakdown of response codes is shown with different colors This data includes all response codes served from the Edge server to the end user.
  • Edge Response Codes, as a Percentage of Hits. This graph displays the Edge errors by category for the selected time period and the total percentage of Edge errors. For each response code category, you will see the number of hits and the percentage of all hits. The categories are:
    • OK: 200, 206, and 210
    • Client Disconnect: 408 (WMS) and 432 (Flash)
    • Not-Found: 404
    • Permission: 400, 401, 403, 433 (Flash), and 434
    • Server/Source Error: 500, 501, 502, 503, 504
    • Client-Abort: 000
    • Other: All response codes other than the above, including 301, 302, and 304
      Note: This graph displays response codes based on the stream start times. In the case of a disconnect event for a long-running stream, you will see an apparent increase in the error rate preceding the disconnect, even though the streams end at the same time.
  • CP Code. This table displays the total Hits, Edge Volume, Flash Session Bytes, Total Play Time, and Average Play Time aggregated for the selected CP code. This data includes object bytes plus overhead bytes between the Edge and the end user with all HTTP response codes.

    Flash Session Bytes is the sum of Flash content data (Edge Volume) and Flash non-content session data. The Flash Session Bytes value is slightly larger than Edge Volume for conventional Flash and is the same for HD Flash. This is because conventional Flash sends and receives the non-content session data while the Edge servers for HD Flash presently do not.