Here you'll find a list of the metrics available for use with the various reports dashboards for legacy delivery products, including File Download/HTTP Downloads (FD), HTTP Content Delivery (HCD), and Object Caching (OC).


Metric Name	Description	Limitations of Use
0xx Edge Hits	Number of hits that returned response codes- 0xx (Client Abort)	N/A
2xx Edge Hits	Number of hits that returned response codes - 200 to 299 (Successful)	N/A
200 Edge Hits	Number of hits that returned response code - 200 (Successful)	N/A
206 Edge Hits	Number of hits that returned response code - 206 (Partial Content)	N/A
3xx Edge Hits	Number of hits that returned response codes - 300 to 399 (Redirection)	N/A
302 Edge Hits	Number of hits that returned response code - 302 (Redirection Status Code - Found)	N/A
304 Edge Hits	Number of hits that returned response codes - 304 (Redirection Status Code - Not Modified)	N/A
4xx Edge Hits	Number of hits that returned response codes - 400 to 499 (Client Error)	N/A
4xx Origin Hits	Number of hits from the edge to origin that returned response codes - 400 to 499 (Client Error)	N/A
403 Edge Hits	Number of hits that returned response code - 403 (Forbidden)	N/A
404 Edge Hits	Number of hits that returned the response code - 404 (File not Found)	N/A
404 Object Volume	Size of the content (Object body) transferred to the client in case of 404 responses.	N/A
404 Overhead Volume	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	Number of hits that returned response code - 415 (Unsupported Media Type)	N/A
5xx Edge Hits	Number of hits that returned response codes - 500 to 599 (Server Error)	N/A
5xx Origin Hits	Number of hits from the edge to origin that returned response codes - 500 to 599 (Server Error)	N/A
Other Hits	When a response code received doesn't fall within the codes 2xx to 5xx, it is an Other hit.	N/A
000 Origin Hits	Number hits to the origin that returned the response code - 000 (Client Abort)	N/A
404 Origin Hits	Number hits to the origin that returned the response code - 404 (Not Found)	N/A
2xx Origin Hits	Number hits to the origin that returned the response 200 to 299 (Successful)	N/A
3xx Origin Hits	Number hits to the origin that returned the response codes - 300 to 399 (Redirection)	N/A
4xx Origin Hits	Number hits to the origin that returned the response codes - 400 to 499 (Client Error)	N/A
5xx Origin Hits	Number hits to the origin that returned the response codes - 500 to 599 (Server Error)	N/A
Average Download Time	Average time taken to download content.	N/A
Client Assisted Unicast Error Hits	Total number of hits that result in errors when using Client Accelerated Delivery.	N/A
Customer Origin Bandwidth	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	Total object bytes transferred from the customer origin server to the edge servers.	N/A
Customer Origin Hits	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	Origin offload is the percentage of end-user download requests that reach the origin servers from the <> edge.	N/A
Customer Origin Overhead Volume	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	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	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	Number of download requests received from enduser, during a specific time interval.	N/A
Download Starts	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	Time required to download media based on bandwidth, file size and connection speed.	N/A
Edge + Midgress	Sum of edge and midgress volume. Total bytes, including overhead bytes, transferred from edge servers to the client.	N/A
Edge Attempts	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	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	Total bytes delivered from the edge servers where content was not served from the parent ghost or origin server.	N/A
Edge Hits	All hits to the edge servers from the end-users.	N/A
Edge Errors	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	Number of hits per second to edge servers from end users.	N/A
Edge Error Rate	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 Hits (Partner)	All hits from <>edge servers to the partner.	Partner Reports/Ad Scaler is a feature of <> Adaptive Media Delivery, that helps customers manage the delegation of manifest manipulation to insert advertisements at run-time.
Edge Volume (Partner)	Total bytes transferred from Partner to the <>edge server. Overhead bytes are included. Values provided in GB.	Partner Reports/Ad Scaler is a feature of <> Adaptive Media Delivery, that helps customers manage the delegation of manifest manipulation to insert advertisements at run-time.
Other Hits	When a response code received doesn't fall within the codes 2xx to 5xx, it is an other hit.	Partner Reports/Ad Scaler is a feature of <> Adaptive Media Delivery, that helps customers manage the delegation of manifest manipulation to insert advertisements at run-time.
Edge Manifest Failures	Manifest requests which resulted into errors that returned response codes - 4xx and 5xx	A request is considered a "manifest request" based on the conditions below: For Smooth Streaming Format: Should be an edge hit HTTP method should be GET File extension in URL should be `.ism` /`.isml` HTTP response code should be 4xx or 5xx For HLS Format: First two bytes of byte range request indicated in ghost log. File extension in URL should be `.m3u8` HTTP response code should be 4xx or 5xx Should be an edge hit HTTP method should not be HEAD For HDS Format: File extension in URL should be `.f4m /.f4f / .f4x` HTTP response code should be 4xx or 5xx Should be an edge hit HTTP method should not be HEAD For DASH Format: First two bytes of byte range request indicated in ghost log. File extension in URL should be `.mpd` HTTP response code should be 4xx or 5xx Should be an edge hit HTTP method should not be HEAD
Edge Object Volume	Size of the actual content (Object body) transferred to the client.	N/A
Edge Overhead Volume	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 Plays	Number of times the media was successfully played during a specific time interval. This information is based on successful manifest requests.	A request is considered a manifest request based on the conditions below: For Smooth Streaming Format: Should be an edge hit HTTP method should be GET File extension in URL should be `.ism` /`.isml` HTTP response code should be 200 or 206 For HLS Format: First two bytes of byte range request indicated in ghost log. File extension in URL should be `.m3u8` HTTP response code should be 206 or 304 Should be an edge hit HTTP method should not be HEAD For HDS Format: File extension in URL should be `.f4m / .f4f / .f4x` HTTP response code should be 206 or 304 Should be an edge hit HTTP method should not be HEAD For DASH Format: First two bytes of byte range request indicated in ghost log. File extension in URL should be `.mpd` HTTP response code should be 206 or 304 Should be an edge hit HTTP method should not be HEAD
Edge Secure Volume	Total number of bytes transferred from edge to the end user for assets using Media Encryption, formerly known as SecureMedia	N/A
Edge Streaming Volume	Total number of megabytes of inter-media format fragments transferred from the edge server.	N/A
Edge Streaming Midgress Volume	Total number of megabytes of inter-media format fragments transferred from Parent Server to an edge server, including overhead bytes.	N/A
Edge Throughput	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	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	Total bytes transferred between the edge to the end user. Overhead bytes are included. Values provided in GB.	N/A
Ingress Bandwidth	N/A
Ingress Hits	All the hits from the edge server to origin, this includes customer origin and NetStorage.	N/A
Ingress Volume	Total number of megabytes, including overhead bytes, transferred from the origin to the edge server. This includes NetStorage and customer origins.	N/A
Ingress Hits/sec	Ingress Hits/sec	N/A
Midgress Bandwidth	Total bandwidth usage from one edge server to another, including all HTTP response codes. Volume totals include object and overhead bytes.	N/A
Midgress Object Volume	Total object bytes transferred from one edge server to another edge server.	N/A
Midgress Volume	Total bytes transferred from one edge server to another edge server. Values provided in GB.	N/A
Midgress Hits	Midgress traffic includes hits from edge servers to other edge servers.	N/A
Midgress Hits/sec	Number of hits per second from edge servers to other edge servers. This includes pre-fetched content and inter-media format fragments.	N/A
Midgress Object Volume	Total object bytes transferred from one edge server to another edge server.	N/A
Midgress Overhead Volume	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
Mid-Stream Errors	Total errors, excluding start-up errors, that occurred during stream play.	N/A
NetStorage Bandwidth	Total bandwidth usage at the NetStorage domain, including all HTTP response codes. Volume totals include object and overhead bytes.	N/A
NetStorage Volume	The total bytes transferred from the NetStorage domain to the edge servers.	N/A
NetStorage Hits	All hits from the edge servers to the NetStorage domain.	N/A
Offload (Hits)	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)	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	Total bandwidth usage at the origin servers, including all HTTP response codes. Volume totals include object and overhead bytes.	N/A
Origin Hits	All the hits from the edge server to origin, this includes customer origin and NetStorage and "Your Origin" (custom) origins.	Refer to Knowledge Base Article #5566 for details on why origin traffic can show higher values than those for edge traffic.
Origin Hits/sec	Number of hits per second from the edge server to origin, this includes NetStorage and "Your Origin" (custom) origins.	N/A
Origin Volume	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	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	Total object bytes transferred from the customer origin server to the edge servers.	N/A
Origin Hits	All hits from the edge servers to the customer's origin.	N/A
Origin Hit/sec	Number of hits per second from the edge server to origin, this includes NetStorage and "Your Origin" (custom) origins.	N/A
Origin Overhead Volume	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
Partner Errors	The number of partner hits that resulted in error responses for your URL. It is the sum of all 4xx and 5xx hits.	Partner Reports/Ad Scaler is a feature of <> Adaptive Media Delivery, that helps customers manage the delegation of manifest manipulation to insert advertisements at run-time.
Partner Hits	When a response code received doesn't fall within the codes 2xx to 5xx, it is an other hit.	Partner Reports/Ad Scaler is a feature of <> Adaptive Media Delivery, that helps customers manage the delegation of manifest manipulation to insert advertisements at run-time.
Partner Response Time	Partner response to hits.	Partner Reports/Ad Scaler is a feature of <> Adaptive Media Delivery, that helps customers manage the delegation of manifest manipulation to insert advertisements at run-time.
Peer Volume	The number of bytes received from peer(s).This field is populated for customers using <> Download Manager(DLM or Net Session client)-	N/A
Play Duration	Total time duration for which your media was played.	The following apply to the Play Duration metric: Play duration information is available only for universal streaming. If play duration value is 0, you may need to check if the `<reporting:http-streaming.status>` is enabled in configuration.

Customize metrics

All of the widgets in a report's tab use one or more 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

What's covered here only reflects the metrics in the Media Delivery Reports user interface for these products. However, these legacy products also offer individual API operations you can use to view a list of their available metrics: