This article provides troubleshooting steps for when you receive a memory warning 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.
Adobe Commerce on cloud infrastructure Pro plan architecture
You will receive an 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 Commerce to give customers a standard set using insights from Support and Engineering.
Do!:
Don’t!:
Follow these steps to identify and troubleshoot the cause.
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. If services like Redis or MySQL are the top source of memory consumption, try the following:
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. Refer to Slow performance, slow and long-running crons and Cron job stuck in “running” status in our support knowledge base for troubleshooting steps.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 seven 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 the site into maintenance mode if you have not already. For steps, refer to 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 Adobe Account Team), 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. Refer to Adobe Commerce on cloud infrastructure > Test Deployment > Load and stress testing in our developer documentation.