The Traffic tab (AMD)
Traffic reports for Adaptive Media Delivery (AMD) provide information on the number of hits, the bandwidth at which the media was available, and information on volume and hits per Content Provider (CP) code.
Start by setting up a filter
Use the Filters panel to customize your report. You can set these options:
If you've already set filters for another report's tab in the Adaptive Media Delivery > Historical reports, those filters are automatically applied when you access this tab. If this tab doesn't support one or more of those filters, you'll receive a message.
-
Date Range (Required)*. Click the date range field and determine a range of time you want for report data. See Set the date/time range for a report for more information. You can also set a Time and Timezone for this report. However, certain time zones may not work with this report because data is collected on an hourly basis using the UTC time zone.
-
CP Code (Required)*. A content provider (CP) code is a unique identifier we assign to you for reporting, billing, and monitoring traffic served over the Akamai network. Someone in your organization assigns a friendly name to a CP code when it's created—either via a tool in Akamai Control Center or an API, or with the help of your Akamai account representative. Click each desired CP code to include in the filter or, if you know the name or number of the desired CP code, type it in the Filter field to refine the results. You can also click All to include every CP code.
-
Delivery Format. If you want to filter the results to a specific media format, select it here. The Others selection here applies to all other media formats not listed for selection.
-
IP Version. Select the applicable IP version for traffic—IPV4, IPV6, or All for both.
-
Delivery Type. Select from On Demand, Live, or All for both. (All is the default.)
-
Media Encryption. Determine if you want to include streams that used Media Encryption in your filter. (All is the default.)
-
HTTP Version. Select the desired HTTP version used in the transfer of content.
-
Traffic Type. Select the traffic security level—Non-Secure for HTTP traffic, Premium Secure Traffic for HTTPS secure traffic that uses an Enhanced TLS Edge certificate, Secure Traffic (Shared Certificate) for HTTPS secure traffic that uses the Akamai shared certificate, or Standard Secure Traffic for HTTPS secure traffic that uses a Standard TLS Edge certificate.
-
Ultra Low Latency. Enable this if you've incorporated low latency streaming in your AMD property, via the Enable ULL streaming option in the Content Characteristics behavior. All properly configured HLS and DASH-format live streams that have used low latency will be included in the report.
-
Chunked Transfer. This applies if you're incorporating low latency streaming for DASH via Media Services Live in your AMD property. This specific scenario takes advantage of chunked transfer encoding (CTE), where data is sent to the player in a series of "chunks." The player doesn't have to wait until the complete segment is available. Enable this to include DASH streams that were served in chunks via CTE.
The widgets
Each individual content panel in the reporting tabs is referred to as a "widget." Several widgets make up your report in this tab. Here's an example of the "Volume by CP Code" widget in the Traffic tab:
The "Resolution {time increment}" for each widget indicates how frequently data is gathered.
| Widget | Description |
|---|---|
| Hits | Information on the number of hits per second on target media, including the following:
Note: For data specific to prefetching, see the Prefetched Hits widget.
|
| Bandwidth | The total bandwidth usage at all the servers, including the following:
Note: For data specific to prefetching, see the Prefetched Bandwidth widget.
You should typically see a higher value for Akamai edge server bandwidth. This represents content already accessed from your origin, held in cache, and delivered (quicker) to end users—versus requests to access new content from your origin, that is not yet in cache. This is referred to as "Origin Offload." |
| Volume by CP Code | Information on the volume of content transferred per CP code, categorized by Edge, Midgress, Origin, and Edge + Midgress. You can use the Filter field to filter results by CP code. |
| Hits by CP Code | Information on the number of hits per CP code per second, on target media categorized by Edge, Midgress, and Origin. You can use the Filter field to filter results by CP code. |
| Prefetched Hits | This applies only if you've incorporated Prefetching support in your AMD configuration. Its data is similar to the Hits widget, but as it applies to requests for prefetched objects.
|
| Prefetched Bandwidth | This applies if you've incorporated Prefetching support in your AMD configuration. Its data is similar to the Bandwidth widget, but as it applies to requests for prefetched objects.
|
You can modify your filters
Click 
to further refine the specific data for all widgets in the report. The same options discussed above are available for use.
Toggle between Table and Chart view
Click the table icon (
) or the chart icon (
) to switch between these views in a widget.
Aggregation of data is affected by Chart view
If a widget offers a Chart view that displays a line graph, there is a limit on the number of data points that can be plotted. This limit affects the aggregation of data revealed, based on the range of time you specify. See Widget data aggregation and Chart view for more information.
Analyze data
Click the magnifying glass icon (
) to customize the kind of data that is shown in the widget. See Analyze data shown in a report for more information.
Download the widget's data
Click the download icon (
) in a widget to download a comma-separated value (.csv) data file of the report output.
Updated about 1 year ago