Monitor Stream Packaging (RTMP Ingest/ HDS & HLS output)

The Monitor Stream Packaging (RTMP Ingest/ HDS & HLS output) page displays a list of your currently active streams. It can also display inactive streams if you click Inactive Streams. Information in the table includes:

  • Format. The ingress format of the stream, which is indicated by an Adobe Flash icon for Media Services Live.
  • Stream Name. The name of the stream as it was provisioned and the ingress stream names coming from your encoder.
  • CP Code. The Content Provider code associated with the stream.
  • Viewers. The number of concurrent viewers for the stream.
  • Egress Bit Rate. The current rate of the stream from the Edge to the end users, in bits per second.
  • Ingress Bit Rate. The current rate of the stream from your encoder to the entry point, in bits per second.
  • entry point. The IP addresses of the primary and backup entry points that are obtaining the stream on Media Services Live.
  • Encoder. The IP address of your primary and backup encoders used for the stream.

The same information is provided for inactive streams, except the ingress Stream Names, Viewers, Egress Bit Rate, and Ingress Bit Rate.

In the Active Streams view, the following tables are available for Adobe HTTP Dynamic Streaming and Apple Live Streaming streams:

  • Average Playback Sessions. The estimated average number of concurrent playback sessions.
  • 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 a 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.
  • Traffic Data Breakdown by CP Code. Indicates the total Edge traffic served in the selected time range, sorted by CP code.