element119 / module-admin-redis-report
element119/module-admin-redis-report
A Magento 2 module that displays Redis information in the admin.
element119 | Admin Redis Report
📝 Features
✔️ See a snapshot of the health of Redis from the comfort of the Magento admin
✔️ Visualise historic Redis health statistics
✔️ Supports Magento Open Source, Adobe Commerce, and Mage-OS
✔️ Built in accordance with Magento best practises
✔️ Dedicated module configuration section and custom admin user controls
✔️ Seamless integration with Magento
✔️ Built with developers and extensibility in mind to make customisations as easy as possible
✔️ Installable via Composer
✔️ Theme agnostic
Upcoming
⏳ Ability to filter historic charts by date range
⛔️ Incompatibilities
[!CAUTION]
This module is not compatible with Magento instances that utilise the Redis L2 cache and/or the
Magento\Framework\Cache\Backend\RemoteSynchronizedCacheclass for the Redis backend cache.More information is available in the Magento documentation:
🔌 Installation
Run the following command to install this module:
composer require element119/module-admin-redis-report
php bin/magento setup:upgrade
⏫ Updating
Run the following command to update this module:
composer update element119/module-admin-redis-report
php bin/magento setup:upgrade
❌ Uninstallation
Run the following command to uninstall this module:
composer remove element119/module-admin-redis-report
php bin/magento setup:upgrade
📚 User Guide
Configuration for this module can be found in the Magento admin under Stores -> Settings -> Configuration -> Advanced -> System -> Redis Report.
Redis Report
The Redis information can be found in the admin under System -> Tools -> Redis Report.
Enable/Disable Historic Data
The periodic capture of Redis information can be disabled by setting this option to No. This is set to Yes by
default.
Historic Data Retention Period
The value specified here determines how long Magento will store historic Redis report data, measured in days.
An empty value means data will be kept indefinitely.
📸 Screenshots & GIFs
Admin Configuration
Admin Report
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.5.2 | stable | Fail | Magento 2.4.7-2.4.8 Details | 2025-08-09 18:55:09 |
| 1.5.1 | stable | Not tested | Not yet tested Details | 2024-09-28 13:50:35 |
| 1.5.0 | stable | Not tested | Not yet tested Details | 2024-07-30 18:09:59 |
| 1.4.1 | stable | Not tested | Not yet tested Details | 2024-04-13 17:26:23 |
| 1.4.0 | stable | Not tested | Not yet tested Details | 2023-12-05 23:53:47 |
| 1.3.0 | stable | Not tested | Not yet tested Details | 2023-12-05 20:23:31 |
| 1.2.0 | stable | Not tested | Not yet tested Details | 2023-11-22 01:09:22 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2023-11-22 00:18:57 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2023-11-21 23:03:55 |
Requires 3
| Package | Constraint |
|---|---|
| ext-json | * |
| magento/module-backend | * |
| php | ^7.4 || ~8.0.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0 |
Suggests 1
| Package | Reason |
|---|---|
| ethanyehuda/magento2-cronjobmanager | A module for managing scheduled cron jobs from magento's admin panel |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Warning | 61 | 61 warnings (ruleset: Magento2) — 33 auto-fixable with phpcbf |
| PHPMD | Warning | 3 | 3 rule violations (IfStatementAssignment:2, UnusedFormalParameter:1) |
| Cpd | Pass | 0 | |
| Composer validate | Info | 1 | valid; 1 advisory note (composer validate --strict) |
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from element119
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.