Media Services Live 4 Origin Shield

The reports provide usage details for traffic for origins that use multiple CDNs for delivery. If you’ve enabled multi-CDN for your origin, you can find these reports in ​Control Center​ under MSL4 Origin Shield > Realtime.

To view data in this report:

  1. Click Filters.

  2. Select a CP Code and set a Date range to filter the data for the report.

  3. Click Apply.

  1. You can click the Analyze data icon next to each report for more details. See Analyze data shown in a report for more information.

The report's dashboard uses the parameters in the form of metrics and dimensions.

Metrics

Metric nameDescription
2xx HitsNumber of requests made to the entry point posting objects that returned response codes 200 to 299 (Successful)
3xx HitsNumber of requests made to the entry point posting objects that returned response codes 300 to 399 (Redirection)
4xx HitsNumber of requests made to the entry point posting objects that returned response codes 400 to 499 (Client Error)
5xx HitsNumber of requests made to the entry point posting objects that returned response codes 500 to 599 (Server Error)
Active StreamsStreams active during a selected time period
Average Bitrate

Average amount of data transferred in a unit of time, calculated in terms of bits per second. It is expressed in kbps, Mbps, or Gbps.

Note, that values reported do not include manifest requests.

Average LatencyIndicates the delay between Encoder and Entry Point when sending a unit of media payload.
Average Packet LossMeasures the quality of connection between encoder and entry point.
Provides connection level ratio of data packets (bytes) lost to the data packets (bytes) sent by the encoder.
Average Path TimeAverage time taken from source to destination.
Error RateRate of errors occurring in a unit of time, expressed as a percentage.
HitsTotal number of requests made to the entry point posting objects.

Dimensions

Dimension nameDescription
CP CodeIdentifier assigned to a contract associated with a particular stream.
Chunked Transfer Encoding

You can filter on streams that include the Transfer-encoding: chunked HTTP Header

Note that it's available for streams published with Chunked Transfer Encoding enabled.

Encoder IPIP address of encoder generating the stream.
Entry PointIP address of the Entry Point on which stream is ingested.
File ExtensionFile extension of the ingested object. For example, .mp4 or .m3u8
Stream IDUnique identifier associated with a stream generated by the ​Akamai​ provisioning workflow.
Stream TypeType of stream - Primary or Backup.
TimeSet automatically. Indicates the time in UTC format when the content was ingested.
Unique End Point

The URL path after the Stream ID in the ingest URL.
For manifest files, the file name is part of the Unique End Point.
For segment requests, the file name (last path element) is omitted.
Also indicates the bit rate of the stream.

Examples:
  • For manifest files:
    bph1demo_1/r2/prog_index.m3u8

  • For segment requests:
    bph1demo_5/r2/1474867214

In addition to these metrics and dimensions, you can see data visualizations for Usage by Client CDN, Usage by Client ASN, Usage by Client Country, and Usage by Origin Hostname, as shown in this example: