Skip to main content

How to monitor cache flushes

Page Cache Warmer allows you to track changes to products and site pages and update the cache for them.

note

The module tracks page changes via the updated_at field, and if a page has been modified, a request will be sent to Magento to clear the cache, after which the page will be re-warmed.

All flushes performed by Magento are recorded on the Cache flushes page, together with their reason, while Forbid cache flushing = No. No logging option is needed for this. Enable Log cache flush backtrace only if you also want to see the full backtrace of each flush.

note

If the cache was cleared outside of Magento, such as due to a Varnish reboot, TTL expiration, or the execution of your product import script, our log will not be able to track the event. In this case, refer to other Magento logs to identify the cause of the cache clearing.

tip

You do not need to clear the full page cache on a schedule. See How to keep the cache up to date without scheduled cache cleaning.

How to check why the cache was flushed​

  1. Open the Cache flushes page, find and analyze the data in the table.
  2. If the reason is not enough to find the cause, enable Log cache flush backtrace in Advanced logging. The backtrace of the next flushes is then shown in Inspect trace. If you need to save the flushes to the var/log/cache-warmer-flush.log file, enable Log cache tags into file, and also Log cache flush backtrace into file to add the backtrace.

How to forbid cache flushing​

To prevent the extension from tracking changes and automatically updating the cache, enable the Forbid cache flushing option in the Caching and Behavior settings.

note

If you have enabled Forbid cache flushing, changes on the Category and Product pages won't take effect unless you manually purge the cache from System -> Cache Management, or the cache will expire (depending on the TTL set in the Magento settings).