Cache observability

Easel reports a cache result for every request: HIT, MISS, BYPASS, or STALE. Caching defines each result and explains what makes a response cacheable.

Where to read it

• On the response: the X-Easel-Cache header. It's the authoritative answer to whether Easel reused a cached response. See CDN headers.
• In request details: the Cache section of a request in Logs shows the result as CDN, plus the framework's ISR cache result when there is one. See Requests.
• In the request list: filter Logs by cache result to find every MISS or BYPASS in a window.
• In custom queries: chart the route cache breakdown with Run query on Observability. See Metrics.

A request the firewall blocked or challenged never reaches the cache, so it has no cache result.

Runtime Cache

If your app uses Runtime Cache, the Runtime Cache panel on Observability shows reads, writes, hit rate, and revalidations for getCache() and 'use cache: remote', and storage used in each region against the cache's limit. On Hobby, storage is the workspace's shared cache.

Check a response

1. Request the URL and read X-Easel-Cache.
2. Read Cache-Control and Set-Cookie on the same response.
3. In Logs, filter by cache result and path to see whether the result is consistent across requests.

When the result isn't what you expect, see CDN troubleshooting.

Next steps

• Caching
• Revalidation
• CDN troubleshooting