This article provides troubleshooting steps when you receive a memory critical alert for Adobe Commerce in New Relic. Immediate action is required to remedy the issue. The alert will look something like the following, depending on the alert notification channel you selected.
All versions of Adobe Commerce on cloud infrastructure Pro plan architecture.
You will receive a managed alert in New Relic if you have signed up to Managed alerts for Adobe Commerce and one or more of the alert thresholds have been surpassed. These alerts were developed by Adobe to give customers a standard set using insights from Support and Engineering.
Your site may become non-responsive, (if you are not already experiencing a site outage) if you do any of the “Don’t” actions before you have investigated and solved the cause of the alert.
Follow these steps to identify and troubleshoot the cause.
Because this is a critical alert, it is highly recommended you complete Step 1 before you try to troubleshoot the issue (Step 2 onwards).
Check if an Adobe Commerce support ticket exists. For steps, see Track your support tickets in our support knowledge base. Support may have already received a New Relic threshold alert, created a ticket and started working on the issue. If no ticket exists, create one. The ticket should have the following information:
Use New Relic APM’s Infrastructure page to identify top memory intensive processes. For steps, refer to New Relic Infrastructure monitoring Hosts page > Processes tab:
Check that you are on the latest versions. Newer versions can sometimes fix memory leaks. If you are not on the latest version, consider upgrading. For steps, refer to Adobe Commerce on cloud infrastructure > Services > Change Services in our developer documentation.
If the problem with the service is not version related, try the following:
MySQL: Check for issues like long running queries, Primary keys not defined, and duplicate indexes. For steps, refer to Most Common database Issues in Adobe Commerce on cloud infrastructure in our support knowledge base.
Redis: If Redis is a top source of memory consumption, submit a support ticket.
PHP: If PHP is a top source of memory consumption, review running processes by running
ps aufx in the CLI/Terminal. In the terminal output you will see cron jobs and processes that are currently being executed. Check the output for the processes’ execution time. If there is a cron with a long execution time, the cron may be hanging. For troubleshooting steps, see Slow performance, slow and long running crons and Cron job stuck in “running” status in our support knowledge base.
If you are still struggling to identify the source of the problem, use New Relic APM’s Transaction page to identify transactions with performance issues:
If you cannot identify the cause of increased memory consumption, review recent trends to identify issues with recent code deployments or configuration changes (for example, new customer groups and large changes to the catalog). It is recommended that you review the past 7 days of activity for any correlations in code deployments or changes.
If the above methods do not help you find the cause and/or solution within a reasonable time, request an upsize or place site into maintenance mode if you have not already. For steps, see How to request temp resize in our support knowledge base, and Installation Guide > Enable or disable maintenance mode in our developer documentation.
If the upsize returns the site to normal operations, consider requesting a permanent upsize (contact your CSM), or try to reproduce the problem in your Dedicated Staging by running a load test and optimize queries, or code that reduces pressure on services. See Adobe Commerce on cloud infrastructure > Test Deployment > Load and stress testing in our developer documentation.