Redis Cache Manager & Monitor: setup and help

In your Back Office, open Modules > Module Manager, choose Upload a module, and upload the module ZIP. Install it, then click Configure. On older PrestaShop versions, use the corresponding Modules page.

Your hosting must already provide Redis and the PHP Redis extension for the web PHP runtime. The module manages a connection, dashboard and key browser. It does not install Redis or configure your storefront cache backend.

The Back Office calls the module Redis Dashboard & Key Manager. Open its Configuration screen. Start in Connection. Enter the Redis host, port, optional password, database and an exclusive key prefix. On Docker, use the Redis service name if 127.0.0.1 would point to the PHP container itself.

Before the first save, review Caching > Flush Cache on Config Save, which defaults to Yes. Switch it off if you only want to test the connection. Save, then check the connection result.

The tabs are Connection, Caching and Monitoring. Connection contains the master switch and Redis details. Caching contains the three stored cache preferences and save-time clearing. Monitoring controls dashboard statistics and automatic refresh.

• Enable Module. Turns the Redis dashboard and key browser connection on or off; default: 1. Set it in the Connection tab.
• Redis Host. Sets the Redis hostname or IP address; default: 127.0.0.1. Use the Redis container or service name on Docker hosting.
• Redis Port. Sets the Redis TCP port; default: 6379.
• Redis Password. Sets the Redis authentication password; default: empty. A blank secret field keeps the stored password. Use the secret field clear control to remove it when Redis no longer requires authentication.
• Redis Database Index. Selects the Redis database number; default: 0. Use another number only if your host assigned one.
• Key Prefix. Limits browser searches and prefixed flushes to keys starting with this prefix; default: ps_.
• Enable Object Cache. Stores the module preference for using Redis as a PrestaShop object cache backend; default: 0. The module records this setting but does not rewrite PrestaShop server cache files by itself.
• Enable Session Storage. Stores the module preference for keeping PHP sessions in Redis; default: 0. Server/PHP session handling still needs to be configured by your host or developer.
• Enable Full-Page Cache. Stores the module preference for guest full-page caching; default: 0. This module does not add a storefront page-cache layer on its own.
• Flush Cache on Config Save. Deletes keys matching the configured prefix after a successful configuration save and connection test; default: 1.
• Enable Monitoring Dashboard. Controls whether dashboard statistics load; default: 1. Statistics require the PHP Redis extension and both this switch and Enable Module to be on.
• Dashboard Refresh Interval. Automatically reloads the dashboard at this interval in seconds; default: 30. Set 0 for manual refresh only.

The three cache switches do not activate object caching, PHP session storage or full-page caching. Automatic refresh runs only when the PHP Redis extension is available and the module and monitoring switches are on. It pauses while the tab is hidden or a shared-database flush confirmation is being completed. Refresh uses the clean dashboard URL so it does not repeat a submitted action.

These examples describe connection values; they are not an environment-file import format:

Local service: Redis Host=127.0.0.1, Redis Port=6379, Redis Database Index=0, Key Prefix=shop1_
Docker service: Redis Host=redis, Redis Port=6379, Redis Database Index=0, Key Prefix=shop1_

Use the password supplied by your host. If you manage deployment configuration in PHP, the stored keys are REDIS_HOST, REDIS_PORT, REDIS_AUTH, REDIS_DB, REDIS_PREFIX, FLUSH_ON_SAVE, MONITOR_ENABLED and STATS_REFRESH under ConfigTable::setMultiple('mprinstantredis', [...]).

Open the module dashboard and use its connection test. It reports Redis version, connection details, uptime, memory, hit rate, operations per second, clients, evictions and expiry information. These are Redis server statistics, not measurements limited to your prefix. Total key count is summed from Redis INFO database entries.

Open Key Browser. Pattern defaults to *. Limit defaults to 100 and accepts 1 through 1000. The configured prefix is prepended to your search:

Key Prefix: ps_
Pattern: *           scans ps_*
Pattern: product:*   scans ps_product:*

The list shows the key without the prefix, its type, TTL and size/count. Inspect strings, lists, sets, sorted sets and hashes. List and sorted-set previews are limited to the first 100 entries. Use the row Delete action only for keys you intend to remove. Bulk deletion requests are supported, but Key Browser has no multi-selection controls.

Use Clear Redis Dashboard & Key Manager Namespace for the module's owned namespace. A clear scans and deletes keys with the literal configured prefix. Empty ownership and overlap with another registered owner block deletion. The same ownership checks apply to row deletion and save-time clearing.

For a complete reset, the dashboard exposes Flush Shared Database as a separate operation only when namespace coordination is ready. Review the owners, tick the acknowledgement and type the confirmation phrase shown on the screen. A stale ownership manifest or unavailable coordination blocks the operation. A full flush removes every key in the selected Redis database, including unrelated applications. Review what those keys contain before using it.

1. Save connection details and confirm Redis connection verified.
2. Open the dashboard and check the host and port against your intended Redis instance.
3. Search for a known key in Key Browser. A server key count above zero with no matching browser keys can mean your prefix is wrong.
4. If the extension warning appears, enable php-redis for the PHP runtime that serves the Back Office. Enabling it only for the command line (CLI) is not enough.
5. For connection failure, check network reachability, hostname, credentials and database permissions with your host.
6. If deletion is blocked, check the exclusive prefix and registered owner overlap. Do not broaden the prefix to bypass protection.

Read hit rate with memory and evictions. It is the ratio of Redis hits to hits plus misses across the server. Clearing keys can force cache rebuilds. If Redis also stores sessions or other application data, those applications can be affected by removal.

Use Integrity for module checks. The controller identifiers are AdminMPRInstantRedis for the dashboard, AdminMPRInstantRedisConfig for configuration, AdminMPRInstantRedisBrowser for browsing, and AdminMPRInstantRedisIntegrity for integrity.

Set Enable Module to No to stop normal dashboard/browser connections. Uninstall through Module Manager to remove module configuration and menus. The uninstall routine does not flush Redis or remove the Redis server. Review your host's independent cache/session setup separately.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.