Backlog

Findings you have deferred. They do not lower the health score or send alerts, but every scan still checks them: fixed ones resolve on their own, and any that get more severe return to the open list.

How store health changed over time: the health score, how many issues were open, and every finding that was detected or resolved

CPU, memory, disk, PHP and database activity on this server right now — refreshes every 10 seconds while this tab is open

Availability, response time and incident history for your storefront, API and admin panel

Is cron running, which jobs are failing and why, and every job's schedule, runtime and history

Varnish, Redis, Magento Full Page Cache and OPcache — read-only health checks

Audit of admin access, patching, web exposure, malware indicators and live threats — with evidence and step-by-step fixes

Storefront and admin pages, REST calls and GraphQL resolvers that took longer than the configured threshold, measured on every request including page rendering

JavaScript errors from real visitors’ browsers over the last 14 days, with page, browser and stack trace. Browser-extension noise is filtered out.

CDN Analytics

CloudFront configuration, Varnish cache performance, invalidations & real cache hit/miss trend

WAF Monitor

Web Application Firewall — protection status, rules, IP lists, sampled & server-side blocks

SSL Certificate Monitor

Track certificate expiry for all store domains — automatic alerts before expiry

The server, services and software this store runs on, detected automatically

Quick Fixes

Maintenance actions you can run from the dashboard, with what each one affects before you run it

Who is on the store right now: visitors, the pages and API endpoints they use, bots and signed-in admins

PHP, database, Redis, web server and server settings compared with what a store of this size needs

Who changed what through MageMonitor, and when: quick fixes, settings, findings, scans, reports and alert emails