Reporting metrics (DD)

Here you'll find a list of the metrics available for use with the various reports dashboards for Download Delivery (DD).

Use of these metrics in the Media Delivery Reports UI

All of the widgets revealed in a report's tab use one or more of these metrics by default. However, some of the widgets let you view custom data via the Analyze data () functionality, and you can add or remove metrics. See Analyze data shown in a report for full details.

Metrics and the Media Delivery Reports API

A metric's name can differ slightly between the Media Delivery Reports UI and the Media Delivery Reports API v1. When applicable, both values are listed here. You can also run the "List Download Delivery data stores" operation from the API, and do the following:

  1. Review the response output and locate the data store that represents the type of report data you want.
  2. From that data store, store the id values for the dimensions and metrics you want to use.
  3. Use these id values in the "Get Download Delivery data" operation to view filtered report data.
Note: Some metrics use the same name and are similar in their application, but are tied to specific functionality. Review the description for each and make sure you're using the proper API ID for the dimension you want.

Metrics listing

Available metrics are listed alphabetically in this table.

Metric Name API Metrics Name API ID Description Limitations of Use
0xx Edge Hits 0XX Edge Hits 18 Number of hits that returned response codes- 0xx (Client Abort) N/A
2xx Edge Hits 2XX Edge Hits 21 Number of hits that returned response codes - 200 to 299 (Successful) N/A
200 Edge Hits Same 19 Number of hits that returned response code - 200 (Successful) N/A
206 Edge Hits Same 20 Number of hits that returned response code - 206 (Partial Content) N/A
3xx Edge Hits 3XX Edge Hits 24 Number of hits that returned response codes - 300 to 399 (Redirection) N/A
302 Edge Hits Same 22 Number of hits that returned response code - 302 (Redirection Status Code - Found) N/A
304 Edge Hits Same 23 Number of hits that returned response codes - 304 (Redirection Status Code - Not Modified) N/A
4xx Edge Hits 4XX Edge Hits 28 Number of hits that returned response codes - 400 to 499 (Client Error) N/A
4xx Origin Hits Origin Hits (4xx) 184 Number of hits from the edge to origin that returned response codes - 400 to 499 (Client Error) N/A
403 Edge Hits Same 27 Number of hits that returned response code - 403 (Forbidden) N/A
404 Edge Hits 25 Number of hits that returned the response code - 404 (File not Found) N/A
404 Object Volume Same 32 Size of the content (Object body) transferred to the client in case of 404 responses. N/A
404 Overhead Volume Same 33 Size of the protocol components including request bytes, TCP/IP overhead bytes, Ethernet bytes and UDP/IP overhead bytes served from the edge server to the end-user that returned response code - 404 N/A
415 Edge Hits Same 26 Number of hits that returned response code - 415 (Unsupported Media Type) N/A
5xx Edge Hits 5XX Edge Hits 29 Number of hits that returned response codes - 500 to 599 (Server Error) N/A
5xx Origin Hits Origin Hits (5xx) 185 Number of hits from the edge to origin that returned response codes - 500 to 599 (Server Error) N/A
Other Hits Same 30 When a response code received doesn't fall within the codes 2xx to 5xx, it is an Other hit. N/A
000 Origin Hits Origin Hits (0xx) 539 Number hits to the origin that returned the response code - 000 (Client Abort) N/A
404 Origin Hits Origin Hits (404) 183 Number hits to the origin that returned the response code - 404 (Not Found) N/A
2xx Origin Hits Origin Hits (2xx) 540 Number hits to the origin that returned the response 200 to 299 (Successful) N/A
3xx Origin Hits Origin Hits (3xx) 541 Number hits to the origin that returned the response codes - 300 to 399 (Redirection) N/A
4xx Origin Hits Origin Hits (4xx) 542 Number hits to the origin that returned the response codes - 400 to 499 (Client Error) N/A
5xx Origin Hits Origin Hits (5xx) 543 Number hits to the origin that returned the response codes - 500 to 599 (Server Error) N/A
Akamai Override Same 568 The number of requests coming from a known proxy that have been redirected or denied. A known proxy is one that's been identified by our third party partner, GeoGuard. When setting up Enhanced Proxy Detection with GeoGuard, you can select either of these overrides as an Action to be taken when a proxy request is identified.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Akamai Override % Same 569 The percentage of requests coming from a known proxy that were redirected or denied. A known proxy is one that's been identified by our third party partner, GeoGuard. When setting up Enhanced Proxy Detection with GeoGuard, you can select either of these overrides as an Action to be taken when a proxy request is identified.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Applied Matches Same 570 The total number of requests to Akamai edge servers that matched GeoGuard's proxy categories, based on the ones you've applied in your DD property. For example, if your configuration is set up to use "best practices," this consists of all categories, while if you've set up "advanced," only the specific categories you've enabled are included.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Applied Matches % Same 571 The percentage of requests to Akamai edge servers that matched GeoGuard's proxy categories, based on the ones you've applied in your DD property. For example, if your configuration is set up to use "best practices," this consists of all categories, while if you've set up "advanced," only the specific categories you've enabled are included.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Average Download Time Avg Download Time 118 Average time taken to download content. N/A
Blocked Hits Same 563 The number of requests coming from a known proxy that were denied. A known proxy is one that's been identified by our third party partner, GeoGuard. When setting up Enhanced Proxy Detection with GeoGuard, you can select "Deny" as the Action to be taken when a proxy request is identified.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Blocked Hits % Same 564 The percentage of requests coming from a known proxy that were blocked. A known proxy is one that's been identified by our third party partner, GeoGuard. When setting up Enhanced Proxy Detection with GeoGuard, you can select "Deny" as the Action to be taken when a proxy request is identified.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Client Assisted Unicast Error Hits Same 41 Total number of hits that result in errors when using Client Accelerated Delivery. N/A
Customer Origin Bandwidth Origin Bandwidth 186 Total bandwidth usage at the customer origin servers, including all HTTP response codes. Volume totals include object and overhead bytes. N/A
Customer Origin Object Volume Same 13 Total object bytes transferred from the customer origin server to the edge servers. N/A
Customer Origin Hits Same 12 All hits on the origin servers from edge servers. This includes NetStorage and "Your Origin" (custom) origins.

Refer the knowledge base article #5566 for details on why values for origin traffic are higher than those for edge traffic.

Customer Origin Offload N/A Not available in the API Origin offload is the percentage of end-user download requests that reach the origin servers from the Akamai edge. N/A
Customer Origin Overhead Volume Same 14 Total number of protocol component bytes that include request bytes, TCP/IP overhead bytes, ethernet bytes and UDP/IP overhead bytes served from the origin server to the edge server. N/A
Customer Origin Volume Same 166 Total number of megabytes, including overhead bytes,

Refer to Knowledge Base Article #5566 for details on why origin traffic can show higher values than those for edge traffic.

Download Completed Same 16 Number of downloads served successfully; Entire download was served (HTTP status 200) or the byte range (HTTP status 206) contained the last byte of the download. N/A
Download Requests Same 113 Number of download requests received from end users, during a specific time interval. N/A
Download Starts Same 165 Number of times the download was successfully initiated during a specific time interval. This metric is calculated based on the initial bytes of the Bytes Range Request when the response code is 200 and 206.
Download Time N/A Not available in the API Time required to download media based on bandwidth, file size and connection speed. N/A
Edge + Midgress Same 2 Sum of edge and midgress volume. Total bytes, including overhead bytes, transferred from edge servers to the client. N/A
Edge Attempts Same 105 Number of times end-user attempted to play the media, during a specific time interval.

This information is based on the total manifest requests received.

N/A
Edge Bandwidth Same 221 Total bandwidth usage at the edge servers, including all HTTP response codes, for the CP codes and the time period selected. Volume totals include object and overhead bytes. N/A
Edge Cached Volume Same 7 Total bytes delivered from the edge servers where content was not served from the parent ghost or origin server. N/A
Edge Hits Same 4 All hits to the edge servers from the end-users. N/A
Edge Errors Same 102 Number of hits that resulted in error responses for your URL.

It is the sum of all 4xx and 5xx hits.

N/A
Edge Hits/sec Same 454 Number of hits per second to edge servers from end users. N/A
Edge Error Rate Same 219 Ratio of hits that resulted in error responses to the total number of hits.

Response codes 4xx and 5xx are considered to be Error Hits.

N/A
Edge Object Volume Same 5 Size of the actual content (Object body) transferred to the client. N/A
Edge Overhead Volume Same 6 Total number of protocol component bytes that include request bytes, TCP/IP overhead bytes, ethernet bytes and UDP/IP overhead bytes served from the edge server to the end-user. N/A
Edge Proxy Hits Same 565 The total number of hits toAkamai edge servers that came from a known proxy. A known proxy is one that's been identified by our third party partner, GeoGuard.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Edge Secure Volume Same 8 Total number of bytes transferred from edge to the end user for assets using Media Encryption, formerly known as SecureMedia N/A
Edge Throughput Same 103 Rate of successful delivery of media from the edge server. It is calculated as the total bytes delivered divided by the total time taken by ghost to serve the request. Values provided in Mbps. N/A
Edge Uniques N/A Not available in the API Number of unique viewers accessing your media.

This information is calculated based on a unique combination of client IP addresses and user-agent.

New Media Reports use the 'Probabilistic Unique' method to compute edge uniques, which could display less accurate values when Unique Visitors are fewer in number. The accuracy of the method improves with an increased number of Unique Viewers.
Edge Volume Same 107 Total bytes transferred between the edge to the end user. Overhead bytes are included. Values provided in GB. N/A
Edge Volume (Partner) Not available in with the API N/A Total bytes transferred from Partner to the Akamaiedge server. Overhead bytes are included. Values provided in GB. Partner Reports/Ad Scaler is a feature of Akamai Adaptive Media Delivery, that helps customers manage the delegation of manifest manipulation to insert advertisements at run-time.
Hosting Provider Hits Same 574 The total number of requests to Akamai edge servers that came from a proxy identified as GeoGuard's Hosting Provider ( is_hosting_provider), "optional" category.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Manifest Personalization Success Hits Same 57 The total number of requests on which manifest personalization was successfully applied.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Manifest Personalization Error Hits Same 58 The total number of requests that failed due to issues related to Manifest Personalization.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Midgress Bandwidth Same 453 Total bandwidth usage from one edge server to another, including all HTTP response codes. Volume totals include object and overhead bytes. Applies to all non-prefetched content.
Midgress Object Volume Same 10 Total object bytes transferred from one edge server to another edge server. N/A
Midgress Hits Same 9 Midgress traffic includes hits from edge servers to other edge servers. N/A
Midgress Hits/sec Same 455 Number of hits per second from edge servers to other edge servers. This includes prefetched content and inter-media format fragments. N/A
Midgress Overhead Volume Same 11 Total number of protocol component bytes that include Request bytes, TCP/IP overhead bytes, Ethernet bytes and UDP/IP overhead bytes served from the one edge server to another edge-server. N/A
Midgress Volume Same 116 Total bytes transferred from one edge Akamai server to another edge server. Values provided in GB. Applies to all non-prefetched content.
NetStorage Bandwidth Netstorage Bandwidth 632 Total bandwidth usage at the NetStorage domain, including all HTTP response codes. Volume totals include object and overhead bytes. N/A
NetStorage Volume Netstorage Volume 35 The total bytes transferred from the NetStorage domain to the edge servers. N/A
NetStorage Hits Netstorage Hits 34 All hits from the edge servers to the NetStorage domain. N/A
Offload (Hits) Same 169 Percentage of hits from the edge servers as compared to the hits from the origin server, including NetStorage and "Your Origin" (custom) origins.

(edge hits - Ingress hits) / edge hits * 100

N/A
Offload (Volume) Same 170 Percentage of bytes delivered from the edge servers as compared to the bytes delivered from origin server, including NetStorage and "Your Origin" (custom) origins.

(edge volume - ingress volume) / edge volume * 100

N/A
Origin Bandwidth Same 186 Total bandwidth usage at the origin servers, including all HTTP response codes. Volume totals include object and overhead bytes. N/A
Origin Hits/sec Same 456 Number of hits per second from the edge server to origin. This includes NetStorage and "Your Origin" (custom) origins. N/A
Origin Volume Same 168 Total bytes, including overhead bytes, transferred from the origin to the edge server. This includes NetStorage and "Your Origin" (custom) origins. Values provided in GB.

Refer to Knowledge Base Article #5566 for details on why origin traffic can show higher values than those for edge traffic.

Origin Error Rate Same 220 Ratio of hits at the origin server that resulted in error responses to the total number of hits.

Response codes other than 2xx are all considered as Error Hits.

N/A
Origin Object Volume Same 13 Total object bytes transferred from the customer origin server to the edge servers. N/A
Origin Hits Same 12 All hits from the edge servers to the customer's origin. N/A
Origin Overhead Volume Same 14 Total number of protocol component bytes that include request bytes, TCP/IP overhead bytes, ethernet bytes and UDP/IP overhead bytes served from the origin server to the edge server. N/A
Peer Volume Same 3 The number of bytes received from peer(s).This field is populated for customers using Akamai Download Manager(DLM or Net Session client)- N/A
Proxy Hits Same 573 The total number of requests to Akamai edge servers that came from a proxy identified as GeoGuard's Public Proxy ( is_public_proxy), "must-have" category.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Redirect Hits Same 566 The total number of hits toAkamai edge servers that came from a known proxy and were redirected. A known proxy is one that's been identified by our third party partner, GeoGuard. When setting up Enhanced Proxy Detection with GeoGuard, you can select "Redirect" as the Action to be taken when a proxy request is identified.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Redirect Hits % Same 567 The percentage of hits toAkamai edge servers from a known proxy that were redirected. A known proxy is one that's been identified by our third party partner, GeoGuard. When setting up Enhanced Proxy Detection with GeoGuard, you can select "Deny" as the Action to be taken when a proxy request is identified.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Smart DNS Hits Same 576 The total number of requests to Akamai edge servers that came from a proxy identified as GeoGuard's Smart DNS Proxy ( is_smart_dns_proxy), "must-have" category.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

TOR Exit Hits Same 575 The total number of requests to Akamai edge servers that came from a proxy identified as GeoGuard's TOR Exit Node ( is_tor_exit_node), "must-have" category.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Total Actions Taken Actions Taken 561 The number of requests coming from a known proxy that have been allowed, redirected, or denied. A known proxy is one that's been identified by our third party partner, GeoGuard. When setting up Enhanced Proxy Detection with GeoGuard, you can select any of these "actions" to be taken when a proxy request is identified.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Total Actions Taken % Actions Taken % 562 Based on all requests for your DD content, this is the percentage that came from a known proxy and were allowed, redirected, or denied. A known proxy is one that's been identified by our third party partner, GeoGuard. When setting up Enhanced Proxy Detection with GeoGuard, you can select any of these "actions" to be taken when a proxy request is identified.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

VPN Hits Same 572 The total number of requests to Akamai edge servers that came from a proxy identified as GeoGuard's Anonymous VPN ( is_anonymous_vpn), "must-have" category.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

VPN Data Center Hits VPN Datacenter Hits 577 The total number of requests to Akamai edge servers that came from a proxy identified as GeoGuard's VPN Data Center ( is_vpn_datacenter), "optional" category.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Unique Blacklisted Sessions Same 579 The total number of requests that included a unique revoked token from an access revocation list.

Applies to the Enhanced Proxy Detection with GeoGuard functionality. Only for use with the widgets in the Download Delivery > Historical > Proxy Protection reports.

Overhead volume

Overhead volume for traffic between edge server and end user are the bytes of the requested ARL, TCP/IP overhead, TCP/IP data-packet overhead, TCP/IP acknowledgments overhead, TCP/IP new-connection overhead, UDP/IP overhead, and Ethernet overhead.