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

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 Object Delivery data stores operation from the API, and do the following:

Review the response output and locate the data store that represents the type of report data you want.
From that data store, store the id values for the dimensions and metrics you want to use.
Use these id values in the Get Object 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 Name	API Metric Name	API ID	Description	Limitations of Use
2xx Edge Hits	Same	`21`	Number of hits that returned response codes - 200 to 299 (Successful)	N/A
3xx Edge Hits	Same	`24`	Number of hits that returned response codes - 300 to 399 (Redirection)	N/A
4xx Edge Hits	Same	`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 the response code - 400 (File not Found)	N/A
5XX Edge Hits	Same	`29`	Number of hits that returned response codes - 500 to 599 (Server Error)	N/A
Akamai Override	Same	`707`	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 Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Akamai Override %	Same	`708`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Applied Matches	Same	`709`	The total number of requests to <> edge servers that matched GeoGuard's proxy categories, based on the ones you've applied in your OD 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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Applied Matches %	Same	`710`	The percentage of requests to <> edge servers that matched GeoGuard's proxy categories, based on the ones you've applied in your OD 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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Blocked Hits	Same	`702`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Blocked Hits %	Same	`703`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Customer Origin Hits	Same	`12`	All hits to a customer origin ("Your Origin") from <>edge servers.	N/A
Customer Origin Volume	Same	`171`	Total number of megabytes transferred from a customer origin ("Your origin") to <>edge servers. Overhead bytes are included.	N/A
Edge Bandwidth	Same	`222`	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 Hits	Same	`4`	All hits 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 Errors	Same	`102`	Number of hits that resulted in error responses for your objects. It is the sum of all 4xx and 5xx hits.	N/A
Edge Proxy Hits	Same	`704`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Edge Volume	Same	`44`	Total number of bytes transferred between the Edge to the end user. Overhead bytes are included. Values provided in GB.	N/A
File Size Bucket	Same	`6`	The number of bytes and the size of objects requested, both categorized in buckets of various sizes.	N/A
Hosting Provider Hits	Same	`713`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Midgress Bandwidth	Same	`457`	Total bandwidth usage at <> servers, including all HTTP response codes, for the CP codes and the time period selected. Volume totals include object and overhead bytes.	N/A
Midgress Volume	Same	`43`	Total number of bytes transferred from one Edge server to another Edge server. Values provided in GB.	N/A
Midgress Hits	Same	`9`	Midgress traffic includes hits from Edge servers to other Edge servers.	N/A
NetStorage Hits	`Netstorage Hits`	`34`	All hits from the Edge servers to the NetStorage domain.	N/A
NetStorage Volume	`Netstorage Volume`	`35`	Total bytes transferred from the NetStorage domain to the Edge servers	N/A
Offload (Hits)	Same	`722`	Percentage of hits from <>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	Refer to Knowledge Base Article #5566 for details on why origin traffic can show higher values than those for Edge traffic.
Offload (Volume)	Same	`723`	Percentage of bytes delivered from <>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	Refer to Knowledge Base Article #5566 for details on why origin traffic can show higher values than those for Edge traffic.
Origin Bandwidth	Same	`458`	Total bandwidth usage at the origin server, including all HTTP response codes, for the CP codes and the time period selected. Volume totals include object and overhead bytes. Origin servers include NetStorage and "Your Origin" (custom) origins.	N/A
Origin Hits	Same	`167`	All the hits from the Edge server to origin, this includes 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 Volume	Same	`172`	Total number of 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.
Proxy Hits	Same	`712`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Redirect Hits	Same	`705`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Redirect Hits %	Same	`706`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Smart DNS Hits	Same	`715`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
TOR Exit Hits	Same	`714`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Total Actions Taken	Same	`700`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
Total Actions Taken %	Same	`701`	Based on all requests for your OD 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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
VPN Hits	Same	`711`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.
VPN Data Center Hits	`VPN Datacenter Hits`	`716`	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 & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report.

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.