Health Dashboard

Mage2Expert Health Dashboard is an extension for Magento 2 that gives admins and DevOps teams a single, centralized view of the store's operational health — cron jobs, message queue consumers, indexers, cache, disk space, and application logs — all from one admin page, with no SSH access required. Every monitored service reports a color-coded status (Healthy, Warning, Critical, or Not Configured) together with a plain-language summary, and rolls up into one weighted 0–100 health score on the Overview page. Common remediation actions — retrying a failed cron job, restarting a stuck queue consumer, reindexing, or flushing a cache type — are a single click away, dispatched as background processes so the admin UI is never blocked. For example, a store owner can spot a stalled cron queue before it delays order confirmation emails, or a DevOps engineer can catch a disk usage spike before it takes the checkout offline — both from the same dashboard, without opening a terminal. The extension integrates with Magento's native ACL system for role-based access, and is built entirely on Magento's own core APIs — no third-party libraries, no custom cache or queue logic, and no core code modifications. 

Features

• Weighted Health Score — a single 0–100 score summarizing 11 monitored services, rendered as a progress ring with an Excellent / Good / Warning / Critical label. Per-widget weights are fully configurable, and services that are not in use (such as Redis on a filesystem-cache store) are automatically excluded so they never lower the score.
• Dashboard Overview — color-coded status cards for Magento Status, PHP Status, Database, Redis, Cron, Queue, Cache, Indexer, Disk Usage, Search Engine (Elasticsearch/OpenSearch), and SSL, each linking through to its own detail page.
• Cron Monitor — full job history with status, timestamps, and error messages; a one-click Retry action for failed or missed jobs that re-queues and re-runs them within seconds; CSV export of the last 1,000 schedule rows; configurable stalled-cron detection.
• Queue Monitor — live status for every declared consumer with Start, Stop, and Restart actions plus a Clear Queue action for the pending/failed backlog. Works with both the database queue and RabbitMQ, and consumers are launched as fully detached background processes that keep running independently of the admin request.
• Indexer Health — status, mode, and last-update time for every indexer, mirroring bin/magento indexer:status, with a background "Reindex All" action and a per-indexer Reindex button.
• Cache Health — enabled/disabled status for every registered cache type, with a per-type Flush action, a Refresh action that cleans every enabled type, and a Flush All action that flushes the entire cache storage backend.
• Disk Usage Monitor — total, used, and free space with a color-coded usage bar, plus a directory-by-directory breakdown of var/, pub/media, pub/static, generated/, and var/log against configurable warning and critical thresholds.
• Log Analyzer — critical error and exception counts, the most frequently repeated error message, and a safe live tail for system.log, exception.log, debug.log, and cron.log — fast and memory-safe even on multi-gigabyte log files.
• Email Alerts — sent only when a widget's status actually changes (for example Healthy → Warning), never repeatedly for a status that stays the same, with configurable sender identity and recipient list.
• Automated Metrics Snapshots — a periodic cron job records every widget's status into a dedicated database table, forming the foundation for future historical trend reporting.
• Configurable Thresholds & Weights — disk usage, cron stall window, queue backlog, and SSL expiry thresholds are all editable from Stores → Configuration, alongside per-widget score weights.
• Full Magento ACL — every page, and every mutating action on it (retry, reindex, flush, consumer control, queue clear), has its own access control resource, so support staff can be granted read-only dashboards while destructive actions stay restricted to senior admins.
• Extensible by Design — every widget implements a single, simple interface; developers can register their own custom health checks via dependency injection with no core code changes required.
• Zero Core Code Modifications — built entirely on Magento's own cache, indexer, cron, and message queue APIs. No class rewrites, no preferences, no patches. Safe alongside Magento upgrades and other extensions.

How It Works

After enabling the extension, a new Health Dashboard item appears in the main admin navigation with its own icon, separate from every other top-level menu. Opening it shows the Overview page with the weighted health score and a status card for every monitored service. Clicking any card for Cron, Queue, Indexer, Cache, or Disk opens that widget's dedicated page with full detail and one-click remediation actions. All checks run live on every page load — there is no stale cached data — while a background cron job additionally snapshots every widget's status every five minutes for historical record-keeping, and a second background job checks for status changes every ten minutes and sends an alert email when one occurs. 

Configuration & Alerting

All settings live under Stores → Configuration → Mage2Expert → Health Dashboard, organized into General, Thresholds, Health Score Weights, and Email Alerts groups. Disk usage warning/critical percentages, the cron stalled-detection window, queue backlog thresholds, and SSL expiry warning window are all editable with sensible defaults pre-filled. Each of the 11 monitored widgets has its own configurable weight, so the overall score reflects what matters most to your business. Email alerts use Magento's native email template system and a de-duplication mechanism that fires only on a genuine status transition, keeping notifications useful instead of noisy. 

Use Cases

• Store owners and merchandisers — see at a glance whether the store is healthy without needing technical knowledge of cron, queues, or server internals.
• DevOps and hosting teams — catch a stalled cron queue, a stopped consumer, a runaway log file, or a disk usage spike before it becomes an outage, from a single admin screen.
• Agencies managing multiple Magento stores — give each client's support team a safe, read-only view of store health via Magento's own ACL, while keeping remediation actions restricted to the agency's own admins.
• Stores with heavy order or catalog volume — monitor message queue backlog and indexer status in real time during high-traffic periods such as sales events.
• Development and QA teams — quickly verify that cron, cache, and indexers are in a known-good state after a deployment, without needing terminal access to the server.