Understanding the reason for a cache hit, miss or pass
We just launched a set of features that will help you understand the reason behind a cache hit, miss or pass. Now, when looking at a request, you’ll be able to see the applied caching rules, this can help you debug why an operation was or was not cached as you expected.
If you check the operation details, you’ll see a similar view, this one is particularly useful if you want to change your stellate configuration and understand the impact it will have in your operations. For example, you could change your config, and take a look at your top operations to see how your rules are affecting it.
And in the scenario where a request is a pass, we'll show you a more explicit reason
This is now live at stellate.co, we can't wait for you to try it!