Edge Performance Analytic Fields

Indicates the total number of requests for CDN content that correspond to the criteria specified in the report's first column (e.g., Day, Hour, Protocol, etc.). For the purposes of this field, a hit occurs whenever CDN content is requested, regardless of the status code returned to the client.

Indicates the percentage of requests that correspond to the criteria specified in the report's first column (e.g., Day, Hour, Protocol, etc.). This field is a percentage of the total requests that occurred over the time span covered by the report.

Indicates the average amount of data that was sent from our edge servers to HTTP clients (i.e., web browsers). This average value is calculated solely from the requests that correspond to the criteria specified in the report's first column (e.g., Day, Hour, Protocol, etc.).

Indicates the total amount of data, in bytes, that was sent from edge servers to HTTP clients. This sum is calculated solely from the requests that correspond to the criteria specified in the report's first column (e.g., Day, Hour, Protocol, etc.).

Indicates the average amount of data, in bytes, that was sent from HTTP clients (i.e., web browsers) to edge servers. This average value is calculated solely from the requests that correspond to the criteria specified in the report's first column (e.g., Day, Hour, Protocol, etc.).

Indicates the total amount of data, in bytes, sent from HTTP clients (i.e., web browsers) to edge servers. This sum is calculated solely from the requests that correspond to the criteria specified in the report's first column (e.g., Day, Hour, Protocol, etc.).

Indicates the average amount of data, in bytes, that was sent from CDN and customer origin servers to edge servers. This average value is calculated solely from the requests that correspond to the criteria specified in the report's first column (e.g., Day, Hour, Protocol, etc.).

Indicates the total amount of data, in bytes, received from CDN and customer origin servers by edge servers. This sum is calculated solely from the requests that correspond to the criteria specified in the report's first column (e.g., Day, Hour, Protocol, etc.).

Indicates the rate (e.g., Gigabits per second, Megabits per second, Kilobits per second, etc.) at which edge servers delivered content to HTTP clients (i.e., web browsers). This rate is calculated solely from the requests that correspond to the criteria specified in the report's first column (e.g., Day, Hour, Protocol, etc.).

Indicates the total number of requests for the asset indicated by the File Name column that resulted in a 4xx response code.

Indicates the total number of requests for the asset indicated by the File Name column that resulted in a 5xx response code.

Indicates the total number of requests for the asset indicated by the File Name column that resulted in a 404 Not Found response code.

Indicates the total number of requests for the asset indicated by the File Name column that resulted in a 502 Bad Gateway response code.

Indicates the total number of requests for the asset indicated by the File Name column that resulted in a 503 Service Unavailable response code.

Indicates the total number of requests for the asset indicated by the File Name column that resulted in a 504 Gateway Timeout response code.

View definition.

View definition.

View definition.

This field lists the different types of cache statuses returned by the report.

This field lists the types of requests generated by clients for your CDN account. The type of request that will be generated by a client is determined by the header information (e.g., If-Modified-Since or Cache-Control: no-cache) included with the request for the asset. The types of client requests that are tracked are: normal, refresh, revalidation, and revalidation + refresh.

This field lists the IP addresses for the top 100 clients to request content from your CDN account.

This field lists the CNAMEs for which CDN activity took place during the time period covered by the report. This field includes all edge CNAMEs and the CDN hostname (e.g., can.0001.transactcdn.com). The CDN hostname is included in this list, since it is a CNAME to a server on our network.

Variations in the hostname (i.e., due to case or port) will cause a separate entry to be listed in this field.

This field lists the type of compression used to deliver an asset to a client. The available compression types are bzip2, deflate, gzip, not compressible, and uncompressed.

Indicates the date (Format: YYYY-MM-DDIdentifies a date (e.g., 2024-07-08). This date is determined according to the UTC/GMT time zone.) for which data is being reported.

View definition.

Indicates the CDN URL path to an asset. The CDN URL path always starts with the content access point (e.g., /000001/). The content access point starts directly after the CDN hostname (e.g., can.0001.transactcdn.com).

For the purposes of this field, edge CNAME URLs are converted to their equivalent CDN URLs. This allows an accurate tally for all statistics associated with an asset regardless of the CDN or edge CNAME URL used to request it.

This field lists the file extension (e.g., .swf, .png, .mp4, etc.) and the media type associated with the requested content. This field is formatted as follows: .ext [MediaType].

Indicates the three-letter abbreviation for each POP that handled CDN traffic.

View definition.

This field lists each hour contained within the Hourly report.

Format: YYYY-MM-DD hh:mmIdentifies a date and time (UTC/GMT) using a 24 hour format (e.g., 2024-07-08 15:00).

This field lists the HTTP request methods used to request CDN content. The most common HTTP request methods for this report are GET, HEAD, and POST.

This field lists the HTTP response codes (e.g., 200, 403, 404, etc.) that were returned in response to a request for CDN content.

This field lists the CDN or customer origin servers that hosted CDN content that was requested.

View definition.

This field lists each protocol (i.e., HTTP or HTTPS) used to request CDN content.

This field lists the top 100 referrers that your clients used to request CDN content. A referrer indicates the URL from which a request was generated. This information is typically stored in an HTTP request header.

A dash (-) referrer indicates that the content was hit directly, the referrer was stripped out by the user agent, or the referrer was not passed through the HTTP header.

Indicates a Token-Based Authentication status code. This status code indicates how a request for an asset was handled by Token-Based Authentication.

View definition.

View definition.

View definition.

Indicates the total amount of data transferred for the first instance of each unique asset on that date.

View definition.

Indicates the total number of unique assets that were requested on a particular date. The URL used to access the asset determines whether an asset is unique. If query-string caching has been enabled, then the query string will also be taken into account when determining whether an asset is unique.

For the purposes of this field, edge CNAME URLs are converted to their equivalent CDN URLs. This allows an accurate tally for all statistics associated with an asset regardless of the CDN or edge CNAME URL used to request it.

Indicates the CDN URL path to an asset. The CDN URL path always starts with the content access point. The content access point starts directly after the CDN hostname (e.g., can.0001.transactcdn.com) in a CDN URL. The relative path in the following sample CDN URL is indicated in bold, blue font.

For the purposes of this field, edge CNAME URLs are converted to their equivalent CDN URLs. This allows an accurate tally for all statistics associated with an asset regardless of the CDN or edge CNAME URL used to request it.