Media Services On Demand reports

Progressive Media report

The Progressive Media report lets you see historical data for your Akamai Media Services on Demand: Progressive Media content.

You can access the report from the Reports menu. See How to use reports.

Traffic tab

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

Media CP codes (required). Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.
IP (optional). Supported array values are IPv4 and IPv6. If no IP version is selected, the report shows data for both IPv4 and IPv6.
Traffic (optional). Traffic security level: non-secure traffic for HTTP traffic or secure traffic for HTTPS traffic that uses an enhanced TLS or standard TLS edge certificate, or Akamai shared certificate.

Metrics

📘
This report shows data with a fifteen-minute aggregation.

Offload. Percentage of bytes delivered from Akamai Edge servers versus the bytes delivered from an origin server.
Total bandwidth. Bandwidth usage between all servers, including the following:
- Edge bandwidth. Total number of megabytes transferred from the Edge to the end user. Overhead bytes are included.
- Midgress bandwidth. Total object megabytes transferred from one Edge server to another Edge server. This includes prefetched content and inter-media format fragments. Overhead bytes are included.
- Requests bandwidth. Total number of megabytes transferred in HTTP requests over the time specified.
- Origin bandwidth. Total number of megabytes transferred from the origin to the Edge server. This includes transfers from NetStorage and your custom origins. Overhead bytes are included.
Edge traffic, in hits per second. Total number of hits per second to Edge servers from end users requesting your MSOD content, over the range of time specified. This includes all HTTP response codes.
Edge response codes. Total number of hits for each response code and time period selected, for each five-minute period. This includes all response codes served from the Edge server to the end user. For each category of response code, the report shows the number of Edge hits. The response code categories are:
- OK (200, 201, 204, 206, 210).
- Not-modified (304).
- Redirect (301, 302).
- Not-found (404).
- Permission (401, 403, 415).
- Server error (500, 501, 502, 503, 504).
- Other (All other status codes).
Rate of key 4xx edge responses, per second. Total number of 401, 403, 404, and 415 responses returned for the selected CP codes and time period.
Origin traffic, in hits per second. Total number of hits per second to origin servers, for both NetStorage and your custom origins, including all HTTP response codes, over the date range specified.
CP code traffic details Total hits and Edge volume categorized by CP codes. This data includes object bytes plus overhead bytes between the Edge and the end user, for all HTTP response codes.

URLs tab

HTTP URL data is stored only for URLs with at least 50 hits per day. This means that URLs with less than 50 hits per day are excluded from single day reports and reports that span multiple days will under-report the traffic for some URLs. The 50 hit requirement is in place to prevent customers with a large number of distinct URLs with few hits from overwhelming the reporting systems. This requirement has an impact on data returned by the report. This explains why you may observe differences between URL responses and URL traffic reports.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

Media CP codes (required). Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.
IP (optional). Supported array values are IPv4 and IPv6. If no IP version is selected, the report shows data for both IPv4 and IPv6.
Traffic (optional). Traffic security level: non-secure traffic for HTTP traffic or secure traffic for HTTPS traffic that uses an enhanced TLS or standard TLS Edge certificate, or Akamai shared certificate.
URL (optional). Portion of a URL with report data you want to see.
Trend By Day (optional). URL trend of hits, volume, or response codes per URL per day to show in the report. The options are:
- Show only 'OK volume' per URL. Total number of bytes, including protocols overheads, successfully ('OK') transferred from the Edge to the end user, for each URL.
- Show only 'Error Volume' per URL. Total number of bytes, including protocols overheads, transferred from the Edge to the end user that resulted in an error for each URL.
- Show only 'OK Hits' per URL. Only successful Edge hits for each URL.
- Show only '{Response Code}' per URL. Only hits that resulted in that response code, for the selected date range. Values of "{#}xx" reveal all response codes from that range. For example, 'Show only 3xx per URL' shows hits that resulted in any 300 response (302, 304, etc.).
- Show only 'Offloaded hits' per URL. Number of hits received by the Edge and successfully offloaded to the origin to obtain the target content.
- Show only 'Origin Hits' per URL. Number of hits initiated by the Edge to your origin for each URL, for example, after the Edge has successfully processed a hit from the Client.
Show only 'Origin OK Volume' per URL. Total number of bytes, including protocols overheads, successfully ('OK') transferred from the origin to the Edge, for each URL.
Show only 'Origin Error Volume' per URL. Total number of bytes (including protocols overheads) transferred from the origin to the Edge for hits that resulted in an error, for each URL.

Metrics

Top URLs sorted by volume. Details of the transfer of content for your top URLs, both OK (successful) and resulting in errors, over the date range specified. The URL with the highest number of bytes transferred is listed first.
Top URLs sorted by hits. Details of the transfer of content for your top URLs, both OK (successful) and resulting in errors, over the date range specified. The URL with the highest number of hits is listed first.
Top URLs sorted by errors. Details of the transfer of content for your top URLs, both OK (successful) and resulting in errors, over the date range specified. The URL with the highest number of error hits is listed first.
URL trend by day. Daily trend data for each of the URLs listed. Use the Trend By Day filter to select which data to show.

User locations tab

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

Media CP codes (required). Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.

Metrics

Top countries. Number of all requests, sorted by countries with the most activity.
- OK hits. Number of successful hits from end users to Edge servers.
- OK volume. Total number of bytes, including protocols overheads, successfully transferred from the Edge in that country.
Top U.S. states. Number of requests from the United States, sorted by states with the most activity.
- OK hits. Number of successful hits from end users to Edge servers in that state.
- OK volume. Total number of bytes, including protocols overheads, successfully transferred from the Edge in that state.
Canadian provinces. Number of requests from Canada, sorted by provinces with the most activity.
- OK hits. Number of successful hits from end users to Edge servers, in that province.
- OK volume. Total number of bytes, including protocols overheads, successfully transferred from the Edge in that province.