Solution

Follow these steps to identify and troubleshoot the cause.

  1. To identify the source of the problem, use New Relic APM’s Transaction page to identify transactions with performance issues:

    • Sort transactions by ascending Apdex scores. Apdex refers to user satisfaction to the response time of your web applications and services. A low Apdex score can indicate a bottleneck (a transaction with a higher response time). Usually it is the database, Redis, or PHP. For steps, refer to New Relic View transactions with highest Apdex dissatisfaction.
    • Sort transactions by highest throughput, the slowest average response time, most time-consuming, and other thresholds. For steps, refer to New Relic Find specific performance problems.
  2. Use New Relic APM’s Infrastructure page to identify resource intensive processes. For steps, refer to New Relic Infrastructure monitoring Hosts page > Processes tab.

  3. If services like Redis or MySQL are the top source of memory consumption, try the following:

  4. If the issue is not caused by service versions:

  5. Once a potential source of the issue is identified, SSH into the environment to investigate further. For steps, refer to Cloud for Adobe Commerce > Technologies and requirements > SSH into your environment in our developer documentation.

  6. If you are still struggling to identify the source, 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.

  7. If you are unable to find a solution within a reasonable time, request an upsize or place site into maintenance mode if you have not already done so. 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.

  8. 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 Cloud for Adobe Commerce > Test Deployment > Load and stress testing in our developer documentation.

Previous pageManaged alerts on Adobe Commerce: MariaDB alerts
Next pageManaged alerts for Adobe Commerce: CPU warning alert

Commerce

Adobe Commerce at Summit

Register for these admin sessions:


Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more