Cache analytics

Identify uncached, expired, or ineligible resources to optimize site performance and reduce origin server traffic.

Procedure

In the ESA console, go to Websites and click the target site in the Website column.
In the navigation pane on the left, select Caching > Cache Analytics.

Analytics dashboard

1. Filter data

Filter data by specific criteria or a time range.

Supported filters: Cache Status, Country/Region, Host, HTTP Method, Path, Query String, Content Type, Edge Status Code, Served By, Device Type, and Version (Enterprise plan only).
Supported time ranges: 30 Minutes, 1 Hour, 3 Hours, Today、Yesterday, This Week, Last Week, This Month, Last Month and Custom time range. Among these, 30 Minutes, 1 Hour and 3 Hours are relative duration presets calculated backward from the current time. Today、Yesterday, This Week, Last Week, This Month and Last Month are calendar-based presets based on natural time periods.
After you select Custom, click Select Date to specify a start and end time. The maximum selectable range is determined by your plan quota (up to 31 days).

2. Metrics

Cache performance
- Response Traffic: The total traffic served to clients by ESA edge nodes.
- Requests: The total number of requests from clients.
Cache reserve (Enterprise plan only)
- Data Transfer: The response traffic that flows through cache reserve nodes.

Note

For example, if you select Last 30 Days and requests increase by 2.03%, ESA received 2.03% more requests in that period compared to the previous one.

3. Data overview and trends

Trend graphs show metric changes over time for each dimension. Views other than "All" display only the top five data points and their total.

4. Cache status

Displays data for each cache status. Click a status to filter or exclude it.

Status	Description	Triggering scenarios
MISS	Cache miss. The resource is fetched from the origin server.	A resource is requested for the first time. No cache rules are configured, or the request does not match any configured rule.
HIT	Cache hit. The content is served from the cache.	The requested static resource is cached on an ESA edge node and has not expired. The request matches the configured cache rules.
DYNAMIC	A dynamic resource that is fetched from the origin server.	The requested content is a dynamic resource, such as user session information or personalized data.
EXPIRED	The cached resource has expired and is re-fetched from the origin server, which responds with `200` or `206`.	The cached resource has expired and needs revalidation or a fresh copy. The configured TTL is too short.
BYPASS	The request bypasses the ESA cache and directly accesses the origin server.	ESA is not configured to prioritize the origin server's cache policy, and the cache time in ESA is set to 0. ESA is configured to prioritize the origin server's cache policy, and the origin server's `Cache-Control` header is one of the following: `no-cache`, `no-store`, or `max-age=0`.
STALE	An expired (stale) resource from the cache is served temporarily while revalidation is scheduled.	ESA is configured to prioritize the origin server's cache policy, and the origin response includes `Cache-Control:stale-while-revalidate=<seconds>`. Within the specified time, ESA serves the stale cache to the client while revalidating the resource with the origin server. ESA is set to prioritize the origin server's cache policy, and the origin response includes `Cache-Control:stale-if-error=<seconds>`. Within the specified time, if ESA cannot access the origin server to retrieve the updated resource (for example, the origin server times out), it serves the stale cache to the client. The Serve Expired Cache feature is enabled in ESA. If ESA cannot access the origin server to retrieve an updated resource (for example, the origin server times out), it serves the stale cache to the client.
REVALIDATED	The cached resource expired, but revalidation confirms it has not changed. The cached content is served to the client.	The resource has not changed. ESA sends an `If-Modified-Since` or `If-None-Match` header in the back-to-origin request, and the origin responds with `304`.
NONE/UNKNOWN	The cache status cannot be determined.	Caching is not enabled or is configured incorrectly. The request does not match any cache rules.

5. Top data

Supported data dimensions: Content Type, Path, Host, Device Type, Country/Region, Edge Status Code, and Version (Enterprise plan only).
By default, the top five data points are displayed. Click More to view all data.

6. Print

The page is print-friendly. Print it from your browser to generate a report.

7. Download

Click the download icon in the upper-right corner of the Data Overview and Top Data sections to export data locally.

Supported plans

Free	Basic	Standard	Advanced	Enterprise
Not supported	Not supported	Supported	Supported	Supported