Traffic reports for HTTP Content Delivery (HCD) 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 Object Caching - 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.

IMAGE_STUB

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. This report presents data for a single CP code. Select the desired one from the CP Code drop-down.
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.

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 "Total Bandwidth" widget in the Traffic tab:

IMAGE_STUB


Widget	Description
Total Bandwidth	Bandwidth usage between all servers, including the following: Edge Bandwidth . The total number of megabytes transferred from the Edge to the end user. (Overhead bytes are included.) Origin Bandwidth . The total number of bytes transferred from the origin to the Edge server. (Overhead bytes are included.) This includes NetStorage and "Your" (custom) origins. Midgress Bandwidth . Total object bytes transferred from one Edge server to another Edge server. This includes prefetched content and inter-media format fragments. Total Bandwidth . The total object bytes transferred between all entities in the request (client - Edge Server - origin). Requests Bandwidth . The total volume of requests over the time specified. This also displays the overall volume totals for each bandwidth metric.
Edge Traffic, In Hits Per Second	The number of hits per second from end users to the Edge, over the date range specified. This widget has a resolution of five minutes, meaning data is gathered in five minute intervals.
Edge Response Codes	The number of Edge hits from end users to the Edge for all response codes, over the date range specified. This also displays totals for each response code.
Origin Bandwidth	The total bandwidth usage at the origin servers (both NetStorage and "Your Origin" (custom) origins), including all HTTP response codes, over the date range specified. Volume totals include object and overhead bytes. This also displays the total origin volume transferred.
Origin Traffic, In Hits Per Second	The total number of hits per second to origin servers (for both NetStorage and "Your Origin" (custom) origins), including all HTTP response codes, over the date range specified. This also displays the total number of origin hits.
Origin Response Codes	The frequency and volume of specific HTTP response code hits to origin servers (for both NetStorage and "Your Origin" (custom) origins), over the date range specified. This also displays the total number of hits for each HTTP response code.
Origin Bandwidth Offload	This includes all bandwidth traffic from origin to Edge servers, for all HTTP response codes, over the specified date range. Volume totals include object and overhead bytes. Origin Responses . The total number of bytes transferred from the origin to the Edge server. (Overhead bytes are included.) Edge Responses . The total number of bytes transferred from the Edge to the end user. (Overhead bytes are included.) This widget also displays the overall total Edge Volume and Origin Volume bandwidth. 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).
Edge Page Views, In Page Views Per Second	The total number of page view requests, per second to the Edge, over the specified date range. A "page view" is defined as the delivery of a file that has a "text/html" content type, but excludes redirects (HTTP response code 301/302) and File Not Found error page (HTTP response code 404). A content type is a header that describes the file type that follows, which the browser uses to render the content properly.
CP Code Traffic Details	This widget displays the following, for the date range specified: Overall Totals . The first row lists the total number of Edge hits and Edge volume transferred for all CP codes. Individual CP code totals . The total number Edge hits and Edge volume transferred for that CP code.

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.