Reporting metrics (ACE)
Here you'll find a list of the metrics available for use with the various reports dashboards for Akamai Cloud Embed (ACE—formerly "Wholesale Delivery").
Where can I use these?
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.
The metrics
The metric name can differ slightly between the PORTAL_NAME_INITIAL interface and the Media Delivery Reports API v1. Both values are listed in the table that follows. You can also run the List Akamai Cloud Embed data stores operation in the API and review
id
information for each metric in the response.
Metric Name | API Metric 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 |
404 Edge Hits | Same | 25 | Number of hits that returned response code - 404 (Not Found) | N/A |
5XX Edge Hits | Same | 29 | Number of hits that returned response codes - 500 to 599 (Server Error) | N/A |
Edge Hits | Same | 4 | All hits to the Edge-servers from the end-users. | N/A |
Edge Throughput | N/A | *Not available in the API* | 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 Volume | Same | 44 | Total bytes transferred from the Edge to the end user. Overhead bytes (See below) are included. Values provided in GB. | N/A |
Origin Volume | N/A | *Not available in the API* | Total bytes sent by the origin in response to requests from the <> CDN. | This is only available at the subcustomer ID level. It's not available for the subcustomer domain. |
Origin Hits | Same | 30 | Total hits or requests made from the <> CDN to origin. | This is only available at the subcustomer ID level. It's not available for the subcustomer domain. |
Origin Req Volume | N/A | *Not available in the API* | Total bytes in the requests going from <> CDN to origin. | This is only available at the subcustomer ID level. It's not available for the subcustomer domain. |
Midgress Volume | Same | 43 | 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.
Midgress hits are counted twice, once when the hit is received by an Edge server, and the second time when it performs a hit. | N/A |
Origin Offload | Same | 122 | Percentage of bytes delivered from the Edge servers as compared to the bytes delivered from your origin. | This is only available at the subcustomer ID level. It's not available for the subcustomer domain. |
Other Hits | N/A | *Not available in the API* | When a response code received doesn't fall within the codes 2xx to 5xx, it is an other hit. | N/A |
Total Download Time | N/A | *Not available in the API* | Also referred to as "Throughput," this is the rate of successful delivery of content from the edge server. It's calculated as the total bytes delivered divided by the total time taken by <> servers to serve the request. Values are provided in Mbps. | N/A |
Ingress Hits | 119 | Total ingress hits. Origin or Ingress hits are for traffic from your origin to Akamai edge servers. | ||
Ingress Bytes | 120 | Total ingress response bytes delivered from server to browser. It includes ingress (or origin) traffic. | ||
Ingress Req Bytes | 121 | Total ingress response bytes delivered from server to browser. It includes ingress (or origin) traffic. |
Overhead volume
Overhead bytes 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.
Updated 12 months ago