Cache Reserve metrics show discrepancy between dashboard pages

For Workers & Pages, what is the name of the domain?

(general question - seeking clarification)

What is the issue or error you’re encountering

The read/write metrics are seemingly random, and there’s a discrepancy between the cache-reserve and cache-reserve-analytics dashboard pages.

What steps have you taken to resolve the issue?

I enabled Cache Reserve just yesterday April 9, so it’s been active for just over 24 hours as of this writing. The dashboard cache-reserve page shows 40 reads and 0 writes, whereas the cache-reserve-analytics page shows 7 reads and 4 writes (which seems correct based on my usage/testing). Then after refreshing the cache-reserve-analytics page, it showed 200 reads and 0 writes, and refreshing again showed 1 read and 0 writes. :zany_face:

This is a bit concerning given that we’re charged for these operations. Is there an issue with the Cache Reserve feature right now, or is there something I don’t understand?

Might be related to the recent incident :thinking:

Thanks for the reply, @fritex. I haven’t done any purging by prefix; unless you’re suggesting that what I’m seeing in the dashboard could be some side effect of that issue.

Here’s an example of a discrepancy…

cache-reserve Dashboard Page Shows…


 
 

cache-reserve-analytics Dashboard Page Shows…

 
 

Again, I enabled the feature only yesterday, so both screenshots cover the entirety of the period it’s been in use. (Despite the different terminology, I assume these are referring to the same read/write operations.)

Quick update…

The spurious erroneous read/write stats after page reload have resolved, but there’s still a discrepancy between the cache-reserve and cache-reserve-analytics pages. When I first enabled Cache Reserve, those read/write values agreed between the two pages, but it’s now stuck at 40 reads and 0 writes on the cache-reserve page (as shown in the screenshot), which is incorrect. The values on the analytics page seem correct.
:confused: