Reporting metrics (AMD)

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

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 (IMAGE_STUB) 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 Adaptive Media 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 idvalues for the dimensions and metrics you want to use.

  3. Use theseid values in the Get Adaptive Media Delivery data operation to view filtered report data.

📘

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.

The metrics

Available metrics are listed alphabetically in this table.

Metric NameAPI Metrics NameAPI IDDescriptionLimitations of Use
0XX Edge Hits0XX Edge Hits 18 The number of requests to <> edge servers that returned response codes 0xx (Client Abort)N/A
0XX Edge Hits0xx Hits(Edge) 616 The number of requests to <> edge servers that returned response codes 0xx (Client Abort). This applies to requests for AMD configurations that incorporate the <> Cloud Wrapper service.Only applies if you've incorporated the Cloud Wrapper service with your AMD configuration.
2XX Edge Hits2XX Edge Hits 21 The number of requests to <> edge servers that returned the response code 200 to 299 (Successful)N/A
2XX Edge Hits2XX Hits(Edge) 617 The number of requests to <> edge servers that returned response codes ranging from 200 to 299 (Successful). This applies to requests for AMD configurations that incorporate the <> Cloud Wrapper service.Only applies if you've incorporated the Cloud Wrapper service with your AMD configuration.
200 Edge HitsSame19 The number of requests to <> edge servers that returned the response code 200 (Successful)N/A
206 Edge HitsSame20 The number of requests to <> edge servers that returned the response code 206 (Partial Content)N/A
3XX Edge Hits3XX Edge Hits 24 The number of requests to <> edge servers that returned response codes ranging from 300 to 399 (Redirection)N/A
3XX Edge Hits3XX Hits(Edge) 618 The number of requests to <> edge servers that returned response codes ranging from 300 to 399 (Redirection). This applies to requests for AMD configurations that incorporate the <> Cloud Wrapper service.Only applies if you've incorporated the Cloud Wrapper service with your AMD configuration.
Origin Hits (3xx)Same541 The number hits to your origin that returned response codes in the range 300 to 399 (Redirection)N/A
302 Edge HitsSame22 The number of requests to <> edge servers that returned the response code 302 (Redirection Status Code - Found)N/A
304 Edge HitsSame23 The number of requests to <> edge servers that returned the response code 304 (Redirection Status Code - Not Modified)N/A
4XX Edge Hits4XX Edge Hits 28 The number of requests to <> edge servers that returned response codes ranging from 400 to 499 (Client Error)N/A
4XX Edge Hits4xx Hits(Edge) 619 The number of requests to <> edge servers that returned response codes ranging from 400 to 499 (Client Error). This applies to requests for AMD configurations that incorporate the <> Cloud Wrapper service.Only applies if you've incorporated the Cloud Wrapper service with your AMD configuration.
403 Edge HitsSame27 The number of requests to <> edge servers that returned the response code 403 (Forbidden)N/A
404 Edge Hits25 The number of requests to <> edge servers that returned the response code 404 (File not Found).N/A
404 Object VolumeSame32 The size of the content (Object body) transferred to the client as a result of a 404 response.N/A
404 Overhead VolumeSame33 The 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 HitsSame26 The number of requests to <> edge servers that returned the response code 415 (Unsupported Media Type).N/A
5XX Edge Hits5xx Edge Hits 29 The number of requests to <> edge servers that returned response codes ranging from 500 to 599 (Server Error.)N/A
5XX Edge Hits5xx Hits(Edge) 620 The number of requests to <> edge servers that returned response codes ranging from 500 to 599 (Server Error). This applies to requests for AMD configurations that incorporate the <> Cloud Wrapper service.Only applies if you've incorporated the Cloud Wrapper service with your AMD configuration.
6XX Edge Hits6xx Hits(Edge) 621 The number of requests to <> edge servers that returned response codes ranging from 600 to 699 (Global Error). This applies to requests for AMD configurations that incorporate the <> Cloud Wrapper service.Only applies if you've incorporated the Cloud Wrapper service with your AMD configuration.
Access Revoked RequestsSame578 The total number of hits per second that included any token from an access revocation list.Applies to the Token-based Access Revocation functionality offered with AMD. Only for use with the widgets in the Adaptive Media Delivery > Historical > Content Protection report.
<> OverrideSame568 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, GeoComply via their GeoGuard product. 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 Token-based Access Revocation functionality offered with AMD. Only for use with the widgets in the Adaptive Media Delivery > Historical > Content Protection report.
<> Override %Same569 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, GeoComply via their GeoGuard product. 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Applied MatchesSame570 The total number of requests to <> edge servers that matched GeoGuard's proxy categories, based on the ones you've applied in your AMD 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Applied Matches %Same571 The percentage of requests to <> edge servers that matched GeoGuard's proxy categories, based on the ones you've applied in your AMD 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Average Download TimeAvg Download Time 118 Average time taken to download content.N/A
Average Playback SessionsSame538 The estimated average number of concurrent playback sessions for Stream Packaging.This measure is accurate only for Stream Packaging scenarios.
Blocked HitsSame563 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, GeoComply via their GeoGuard product. 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Blocked Hits %Same564 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, GeoComply via their GeoGuard product. 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Client Assisted Unicast Error HitsSame41 Total number of hits that result in errors when using Client Accelerated Delivery.N/A
Customer Origin BandwidthOrigin 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 VolumeSame13 Total object bytes transferred from the customer origin server to the edge servers.N/A
Customer Origin HitsSame12 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 <> edge.N/A
Customer Origin Overhead VolumeSame14 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 VolumeSame166 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 CompletedSame16 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 RequestsSame113 Number of download requests received from end users, during a specific time interval.N/A
Download StartsSame165 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 + MidgressSame2 Sum of edge and midgress volume. Total bytes, including overhead bytes, transferred from edge servers to the client.N/A
Edge AttemptsSame105 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 BandwidthSame221 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 VolumeSame7 Total bytes delivered from the edge servers where content was not served from the parent ghost or origin server.N/A
Edge HitsSame4 All hits to the edge servers from the end-users.N/A
Edge ErrorsSame102 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/secSame454 Number of hits per second to edge servers from end users.N/A
Edge Error RateSame219 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)*Not available in with the API*N/AAll 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 Manifest Failures*Not available in the API*N/AManifest requests which resulted into errors that returned response codes - 4xx and 5xxA 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 VolumeSame5 Size of the actual content (Object body) transferred to the client.N/A
Edge Overhead VolumeSame6 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 PlaysSame164 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 Proxy HitsSame565 The total number of hits to <> edge servers that came from a known proxy. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product.Applies to the Enhanced Proxy Detection & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Edge Secure VolumeSame8 Total number of bytes transferred from edge to the end user for assets using Media Encryption, formerly known as SecureMediaN/A
Edge Streaming Volume*N/A**Not available in the API*Total number of megabytes of inter-media format fragments transferred from the edge server.N/A
Edge Streaming Midgress Volume49 Total number of megabytes of inter-media format fragments transferred from Parent Server to an edge server, including overhead bytes.N/A
Edge ThroughputSame103 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 VolumeSame107 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/ATotal 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.
Failover Count*Not available in with the API*N/AThe number of times origin failures occurred and fail actions were executed, in support of the Origin Failover functionality for AMDApplies to the AMD Origin Failover functionality. Only for use with the Adaptive Media Delivery > Historical > Availability > Origin Failover widget.
Hosting Provider HitsSame574 The total number of requests to <> edge servers that came from a proxy identified as GeoGuard's Hosting Provider ( is_hosting_provider ), "optional" category.Applies to the Enhanced Proxy Detection & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Manifest Personalization Success HitsSame57 The total number of requests on which manifest personalization was successfully applied.Applies to the Manifest Personalization functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Manifest Personalization reports.
Manifest Personalization Error HitsSame58 The total number of requests that failed due to issues related to Manifest Personalization.Applies to the Manifest Personalization functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Manifest Personalization reports.
Midgress BandwidthSame453 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.
MidgressSame551 The total bandwidth usage at <> edge servers by other edge servers, for the CP code(s) and time period selected.This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Midgress Object VolumeSame10 Total object bytes transferred from one edge server to another edge server.N/A
Midgress HitsSame9 Midgress traffic includes hits from edge servers to other edge servers.N/A
Midgress Hits/secSame455 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 VolumeSame11 The total number of protocol component bytes transferred. This includes request bytes, TCP/IP overhead bytes, Ethernet bytes and UDP/IP overhead bytes served from the one <> edge server to another.N/A
Mid-Stream ErrorsSame114 The total number of errors, excluding start-up errors, that occurred during stream play.N/A
Midgress VolumeSame116 The total bytes transferred from one <> edge server to another. Values are provided in GB.Applies to all non-prefetched content.
Midgress VolumeSame580 The total prefetched bytes transferred from one <> edge server to another. Values are provided in GB.This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

NetStorage BandwidthNetstorage Bandwidth 632 The total bandwidth usage at the NetStorage domain, including all HTTP response codes. Volume totals include object and overhead bytes.N/A
NetStorage VolumeNetstorage Volume 35 The total bytes transferred from the NetStorage domain to the edge servers.N/A
NetStorage HitsNetstorage Hits 34 All hits from the edge servers to the NetStorage domain.N/A
Offload (Hits)Same169 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)Same170 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 BandwidthSame186 Total bandwidth usage at the origin servers, including all HTTP response codes. Volume totals include object and overhead bytes.N/A
Origin HitsSame167 The total number of hits from the <> edge server to origin, this includes customer origin and NetStorage and "Your Origin" (custom) origins.Applies to all non-prefetched content.

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

Origin Hits/secSame456 Number of hits per second from the edge server to origin. This includes NetStorage and "Your Origin" (custom) origins.N/A
Origin Hits (0xx)Same539 The number of hits to your origin that returned the response code 000 (Client Abort).N/A
Origin Hits (0xx)0xx Hits(Origin) 623 The number of hits to your origin that returned the response code 000 (Client Abort). This applies to requests for AMD configurations that incorporate the <> Cloud Wrapper service.Only applies if you've incorporated the Cloud Wrapper service with your AMD configuration.
Origin Hits (2xx)540 The number hits to your origin that returned response codes in the range 200 to 299 (Successful)N/A
Origin Hits (5xx)Same543 The number hits to your origin that returned response codes in the range 500 to 599 (Server Error)N/A
Origin Hits (4xx)Same184 The number of requests to <> edge servers that returned response codes ranging from 400 to 499 (Client Error)N/A
Origin Hits (4xx)Same542 The number of requests to <> edge servers that returned response codes ranging from 400 to 499 (Client Error)N/A
Origin Hits (400)Same188 The number of hits to you origin that returned the response code 400 (Bad Request)N/A
Origin Hits (404)Same183 The number of hits to you origin that returned the response code 404 (Not Found)N/A
Origin Hits (5xx)Same185 The number of hits from <> edge servers to your origin that returned response codes ranging from 500 to 599 (Server Error).N/A
Origin VolumeSame168 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.Applies to all non-prefetched content.

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

Origin Error RateSame220 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 VolumeSame13 Total object bytes transferred from the customer origin server to the edge servers.N/A
Origin HitsSame12 All hits from the edge servers to the customer's origin.N/A
Origin Overhead VolumeSame14 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
Other HitsSame30 The number of requests to <> edge servers that returned a response that doesn't fall within the 2xx to 6xx code range.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 HitsOther Hits(Edge) 622 The number of requests to <> edge servers that returned a response that doesn't fall within the 2xx to 6xx code range. This applies to requests for AMD configurations that incorporate the <> Cloud Wrapper service.Only applies if you've incorporated the Cloud Wrapper service with your AMD configuration.
Partner Errors*Not available in the API.*N/AThe 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 an AMD feature that helps you manage the delegation of manifest manipulation to insert advertisements at run-time.
Partner Hits*Not available in the API.*N/AWhen a response code received doesn't fall within the codes 2xx to 5xx, it is an other hit.Partner Reports/Ad Scaler is an AMD feature that helps you manage the delegation of manifest manipulation to insert advertisements at run-time.
Partner Response Time*Not available in the API.*N/APartner response to hits.Partner Reports/Ad Scaler is an AMD feature that helps you manage the delegation of manifest manipulation to insert advertisements at run-time.
Peer VolumeSame3 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 DurationSame1 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.

Prefetch EfficiencySame560 The percentage of prefetched objects that were actually delivered, compared to the total number requested for prefetching.This is only available if you've added the Prefetching functionality to your AMD property.

For use with the Prefetch Efficiency widget in the Adaptive Media Delivery > Realtime report, only.

Prefetched Midgress HitsPrefetch Midgress Count 47 The total number of hits from Edge Servers to other Edge Servers for the CP codes and time period selected.This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetched Midgress BandwidthMidgress 551 Bandwidth usage at the Edge servers by other Edge servers for the CP codes and time period selected.This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetch Midgress VolumeSame48 Total bytes transferred from parent server to an edge server when content is prefetched.This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetched Origin Bandwidth*N/A**Not available in the API*Bandwidth usage at the Origin servers by Edge servers for the CP codes and time period selected.This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetched Origin Hits*N/A**Not available in the API*The total number of hits on the origin servers from Edge Servers for the CP codes and time period selected.This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetched Origin Hits (0xx)*N/A**Not available in the API*The number of hits from the edge to an origin that returned response codes - 0xx (Client Abort)This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetched Origin Hits (2xx)*N/A**Not available in the API*The number of hits from the edge to an origin that returned response codes - 200 to 299 (Successful).This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetched Origin Hits (3xx)*N/A**Not available in the API*The number of hits from the edge to an origin that returned response codes - 300 to 399 (Redirection).This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetched Origin Hits (4xx)*N/A**Not available in the API*The number of hits from the edge to an origin that returned response codes - 400 to 499 (Client Error).This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetched Origin Hits (5xx)*N/A**Not available in the API*The number of hits from the edge to an origin that returned response codes - 500 to 599 (Server Error).This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Prefetched Origin Hits (xxx)*N/A**Not available in the API*The number of hits from the edge to an origin that returned a response code that was not 2xx, 3xx, 4xx, or 5xx.This is only available if you've added the Prefetching functionality to your AMD property.

It's only applicable in the prefetching-related widgets in the Traffic tab (AMD) and Availability tab (AMD) reports.

Proxy HitsSame573 The total number of requests to <> 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Redirect HitsSame566 The total number of hits to<> 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, GeoComply via their GeoGuard product. 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Redirect Hits %Same567 The percentage of hits to<> edge servers from a known proxy that were redirected. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Smart DNS HitsSame576 The total number of requests to <> 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
TOR Exit HitsSame575 The total number of requests to <> 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Total Actions TakenActions 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, GeoComply via their GeoGuard product. 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Total Actions Taken %Actions Taken % 562 Based on all requests for your AMD 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, GeoComply via their GeoGuard product. 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
VPN HitsSame572 The total number of requests to <> 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
VPN Data Center HitsVPN Datacenter Hits 577 The total number of requests to <> 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 & AMD functionality. Only for use with the widgets in the Adaptive Media Delivery > Historical > Proxy Protection reports.
Unique Revoked SessionsSame579 The total number of requests that included a unique revoked token from an access revocation list.Applies to the Enhanced Proxy Detection & AMD functionality. Only for use with the widgets in the Adaptive Media 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.