The Traffic tab (FD)
Traffic reports for File Download (FD) 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:
- 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 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.
- IP Version. Select the applicable IP version for traffic—IPV4, IPV6, or All for both.
- Delivery Options. Select the traffic security level—Non Secure Traffic for non-secure traffic delivered via HTTP, Secure Traffic for all secure traffic delivered via HTTPS, including Standard TLS certificate, Enhanced TLS certificate, and the Akamai shared certificate, or All Traffic for all security levels.
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 "Total Bandwidth" widget in the Traffic tab:
|Total Bandwidth|| Bandwidth usage between all the servers, including the
|Edge Traffic||The volume of all hits from the end user to the Edge, over the date range specified.|
|Edge Response Codes||The volume of Edge hits from the end user to the Edge for all response codes, over the date range specified.|
|Rate of Key 4xx Edge Responses||The frequency and volume of 400 range HTTP response codes (Bad Request-related) returned, over the date range specified.|
|Origin Bandwidth||The total bandwidth usage at the origin servers, including all HTTP response codes, over the date range specified. Volume totals include object and overhead bytes.|
|Origin Traffic||The total number of hits to origin servers, including all HTTP response codes, over the date range specified.|
|Origin Response Codes||The frequency and volume of specific HTTP response code hits to origin servers, over the date range specified. This also includes the total number of hits for each HTTP response code.|
|Origin Bandwidth Offload||This includes all traffic from origin to Edge servers, for all HTTP
response codes, over the specified date range. Volume totals include object and
Note: A higher total for Edge Bandwidth can represent content that was already requested from an origin and held in the Edge cache (and then delivered to requesting end users).
|CP Code Traffic Details||By default, this widget displays the following, for the date range
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.