You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3. For each report, you can select a date range from the **Date Range** list. You can either select a pre-defined date range, such as **Today** or **This Week**, or you can select **Custom** and manually enter a date range by clicking the calendar icons. After you have selected the date range, click **Go** to generate the report.
44
+
45
+
4. If you want to export the data in Excel format, click the Excel icon above the **Go** button.
46
+
43
47
## Bandwidth
44
-
The bandwidth report consists of a graph and data table that indicates the bandwidth usage for HTTP and HTTPS over a particular time period. You can view the bandwidth usage across all CDN POPs or a specific CDN POP. This report allows you to view the traffic spikes and distribution across CDN POPs in Mbps.
48
+
The bandwidth report consists of a graph and data table that indicates the CDN bandwidth usage for HTTP and HTTPS over a particular time period, in Mbps. You can view the bandwidth usage across all POPs or for a particular POP. This report allows you to view the traffic spikes and distribution for POPs.
45
49
46
-
* Select All Edge Nodes to see traffic from all nodes or choose a specific region/node from the dropdown list.
47
-
* Select Date range to view data for today/this week/this month, etc. or enter custom dates, then click **go** to make sure your selection is updated.
48
-
* You can export and download the data by clicking the excel sheet icon located next to **go**.
50
+
* From the **Edge Nodes** list, select **All Edge Nodes** to see traffic from all nodes or select a specific region.
This report consists of a graph and data table that indicated the traffic usage for HTTP and HTTPS over a particular time period. You can view the traffic usage across all CDN POPs or a particular POP. This report allows you to view the traffic spikes and distribution across CDN POPs in GB.
57
+
This report consists of a graph and data table that indicates the CDN traffic usage for HTTP and HTTPS over a particular time period, in GB. You can view the traffic usage across all POPs or for a particular POP. This report allows you to view the traffic spikes and distribution across POPs.
56
58
57
59
* Select All Edge Nodes to see traffic from all notes or choose a specific region/node from the dropdown list.
58
-
* Select Date range to view data for today/this week/this month, etc. or enter custom dates, then click **go** to make sure your selection is updated.
59
-
* You can export and download the data by clicking the excel sheet icon located next to **go**.
60
60
61
61
The report is updated every five minutes.
62
62
@@ -65,9 +65,6 @@ The report is updated every five minutes.
65
65
## Hits (status codes)
66
66
This report describes the distribution of request status codes for your content. Every request for content generates an HTTP status code. The status code describes how edge POPs handled the request. For example, a 2xx status code indicates that the request was successfully served to a client, while a 4xx status code indicates that an error occurred. For more information about HTTP status codes, see [status codes](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes).
67
67
68
-
* Select Date range to view data for today/this week/this month, etc. or enter custom dates, then click **go** to make sure your selection is updated.
69
-
* You can export and download the data by clicking the excel sheet located next to **go**.
70
-
71
68
72
69
73
70
## Cache statuses
@@ -80,8 +77,6 @@ This report describes the distribution of cache hits and cache misses for client
80
77
* TCP_MISS: Served from Origin. The object was not in the cache and the response was back to origin.
81
78
* TCP_EXPIRED _MISS: Served from origin after revalidation with origin. The object was in the cache, but had exceeded its max-age. A revalidation with origin resulted in the cache object being replaced by a new response from origin.
82
79
* TCP_EXPIRED _HIT: Served from Edge after revalidation with origin. The object was in cache but had exceeded its max-age. A revalidation with the origin server resulted in the cache object being unmodified.
83
-
* Select Date range to view data for today/this week/this month, etc. or enter custom dates, then click **go** to make sure your selection is updated.
84
-
* You can export and download the data by clicking the excel sheet icon located next to **go**.
85
80
86
81
### Full list of cache statuses
87
82
* TCP_HIT - This status is reported when a request is served directly from the POP to the client. An asset is immediately served from a POP when it is cached on the POP closest to the client and has a valid time-to-live (TTL). TTL is determined by the following response headers:
@@ -94,11 +89,11 @@ This report describes the distribution of cache hits and cache misses for client
94
89
95
90
An expired request typically results in a revalidation request to the origin server. For a TCP_EXPIRED _HIT to occur, the origin server must indicate that a newer version of the asset does not exist. This situation typically results in an update of the asset's Cache-Control and Expires headers.
96
91
* TCP_EXPIRED _MISS - This status is reported when a newer version of an expired cached asset is served from the POP to the client. This status occurs when the TTL for a cached asset is expired (for example, expired max-age) and the origin server returns a newer version of that asset. This new version of the asset is served to the client instead of the cached version. Additionally, it is cached on the edge server and the client.
97
-
* CONFIG_NOCACHE - This status indicates that a customer-specific configuration on our edge POP prevented the asset from being cached.
92
+
* CONFIG_NOCACHE - This status indicates that a customer-specific configuration the edge POP prevented the asset from being cached.
98
93
* NONE - This status indicates that a cache content freshness check was not performed.
99
94
* TCP_ CLIENT_REFRESH _MISS - This status is reported when an HTTP client, such as a browser, forces an edge POP to retrieve a new version of a stale asset from the origin server.
100
95
101
-
By default, our servers prevent an HTTP client from forcing our edge servers to retrieve a new version of the asset from the origin server.
96
+
By default, the servers prevent an HTTP client from forcing the edge servers to retrieve a new version of the asset from the origin server.
102
97
* TCP_ PARTIAL_HIT - This status is reported when a byte range request results in a hit for a partially cached asset. The requested byte range is immediately served from the POP to the client.
103
98
* UNCACHEABLE - This status is reported when an asset's Cache-Control and Expires headers indicate that it should not be cached on a POP or by the HTTP client. These types of requests are served from the origin server.
104
99
@@ -119,19 +114,13 @@ The report doesn't include:
119
114
120
115
The formula is: (TCP_ HIT/(TCP_ HIT+TCP_MISS))*100
121
116
122
-
* Select Date range to view data for today/this week/this month, etc. or enter custom dates, then click **go** to make sure your selection is updated.
123
-
* You can export and download the data by clicking the excel sheet icon located next to **go**.
124
-
125
117
126
118
127
119
## IPV4/IPV6 Data transferred
128
120
This report shows the traffic usage distribution in IPV4 vs IPV6.
129
121
130
122
131
123
132
-
* Select Date range to view data for today/this week/this month, etc. or enter custom dates.
133
-
* Then, click **go** to make sure your selection is updated.
134
-
135
124
## Considerations
136
125
Reports can only be generated within the last 18 months.
0 commit comments