Skip to main content

How to check store health

After performing Magento updates or installing new modules, conflicts may occur between extensions from different vendors. This can lead to incorrect website behavior, decreased performance, and a poor customer experience.

tip

To get a quick overview of the site’s condition, use the Alerts tab.

General approach to troubleshooting issues​

  1. Navigate to the Performance section and check the latest generated Snapshot. Compare the metrics with previous snapshots.

  2. If the Snapshot contains errors, go to the Errors tab to get more details. The extension reports three types of errors:

    TypeDescription
    PHP ErrorLow-level PHP errors — fatal code failures. Usually mean the execution stopped due to syntax error, missing file, insufficient memory, or call to an undefined method. (e.g: Fatal error: Uncaught Error: Call to undefined method ..., Warning: require_once(...): failed to open stream, Allowed memory size exhausted).
    PHP ExceptionExceptions generated by Magento’s business logic layer. These don’t break PHP itself but indicate a logical or data-handling problem. (e.g: No such entity with ID = ..., Product not found, Invalid argument supplied, Could not save entity).
    JS ErrorJavaScript errors on the frontend. They don’t affect the backend, but break user interactions — buttons, forms, cart, or widgets stop working. (e.g: Uncaught ReferenceError: ... is not defined, TypeError: Cannot read properties of undefined, Failed to load resource: the server responded with a status of 404).
    note

    The Health Monitoring Suite only reports errors — it does not fix them automatically.

  3. Carefully read the error message and the URL where it appears. Try to reproduce the issue or identify what user action causes it.

  4. Analyze the stack trace (backtrace). Open var/log/system.log and var/log/exception.log (for JS errors — use the browser Console). Check which classes or methods are called just before the error, and determine which vendor/module caused it.

  5. For PHP Exceptions, review the Conflicts tab - a third-party extension may be overriding a critical Magento class or method.

    note

    Remember: these are possible conflicts, not guaranteed issues. Review the logic before making changes.

  6. Review recent changes: Magento or module updates, theme edits, PHP version changes, or enabling/disabling extensions. If the issue appeared after an update, compare versions and dependencies.

  7. Localize and isolate the problem. Temporarily disable the suspected module and see if the error disappears. For frontend issues, disable JS minification/bundling, clear cache, and regenerate static files.

  8. Fix the error, or contact the developer of the affected extension if it’s a third-party module.

  9. Return to the Performance section and check site health after applying fixes. Wait for the next snapshot and review its metrics. If you want to generate a snapshot without waiting for the cron schedule, use the CLI command.

PHP Error (low-level)​

  • Check compatibility of the PHP version and installed extensions.
  • Restore or update the module mentioned in the backtrace.
  • Regenerate static content and clear caches.

PHP Exception (business logic)​

  • Verify data integrity (ensure the entity/ID exists and arguments are valid).
  • Review Conflicts to check for overridden classes.
  • Rebuild indexes and verify migrations or updates.

JS Error (frontend)​

  • Check the Console and Network tabs in the browser to ensure all resources are loaded.
  • Disable JS bundling/minification and redeploy static files.
  • Review custom theme scripts and ensure compatibility with your Magento version.