Troubleshoot performance using New Relic on Adobe Commerce

Issue

Troubleshooting

Resources

Low Apdex score:

Your New Relic Apdex score measures users’ satisfaction with the response time of your web applications and services.

Log in to New Relic > APM > Overview. On the right side of the Overview page, you see the Apdex score graph. An Apdex score of 0.5 or less is a point of concern and warrants investigation.

Web-transaction times (server requests):

1. Log in to New Relic > APM > Select an app > Overview. Set the filter to Web transactions time on the main chart drop-down filter. In the Transactions table, look for App server time. Check for long-running or suspicious transactions.

2. Investigate the transactions individually by going to Monitoring > Transactions. Set the filters to Web and Most time-consuming.

3. Search for third-party modules that consume resources, such as payment providers and ERP systems.

4. In the Monitoring section of APM:

   1. Click Transactions.
   2. Scroll down and click Show all transactions table.
   3. Sort transactions by various parameters and review the transactions that appear suspicious.
   4. Review transactions with a low Apdex score, unusually high Count or Avg time, or Dissat %.
   5. Click each individual transaction. If you can’t resolve the issue, submit a support ticket.
   6. If you need to investigate further, check non-web transactions.

Non-web-transaction time (operations and background tasks):

1. Log in to New Relic > APM > Select an app > Overview. Select Non-web transactions time on the main graph drop-down filter. Click individual transactions in the Transactions table. Look for long-running or suspicious transactions. This includes backend jobs, cron jobs, import and export jobs, and third-party jobs.

To learn more about the New Relic Apdex score, refer to New Relic Documentation > APM Apdex > Measure user satisfaction. Also refer to Managed alerts for Adobe Commerce: Apdex warning alert in the Adobe Commerce support knowledge base.

High CPU usage:

High CPU usage indicates a particularly busy service, such as MySQL or Redis.

1. Log in to New Relic > Infrastructure > Processes.
2. Review the CPU graphs to identify a stuck or high-consuming process that uses more than 100% CPU time, and compare it with the processor count on the instance. Pay attention to peaks in resource utilization. Don’t kill a process unless it is a stuck cron.

To learn more about performance metrics, particularly CPU percentage, I/O bytes, and memory usage for individual processes or groups of processes, refer to New Relic Documentation > Infrastructure UI page > Infrastructure Host page > Processes tab.

High I/O operations: For each customer, this number is individual and differs significantly from the average.

Look for an unusual spike compared with previous average I/O operations:

1. Log in to New Relic > Infrastructure > Processes.
2. Review the I/O Read Bytes Per Second graph.
3. Record the time of the spike.
4. Click APM.
5. Select web transactions time on the main graph drop-down filter.
6. Set the time to the time of the recorded spike.
7. Search for transactions that caused high I/O operations.
8. Drill down into each Transaction trace > Trace details to identify what is causing the issue.

Outage: New Relic determines outages by Apdex. A red line appears on the Apdex score graph when Apdex is < 0.4, which is considered an outage.

Investigating an outage takes several steps, including examining web and non-web transactions, databases, and third-party transactions.

Web Transactions:

1. Log in to New Relic > APM > Overview. Set the filter to Web transactions time on the drop-down graph filter.
2. Manually narrow the time window.
3. Click Transactions. Set the filters to Web and Most time-consuming. Investigate the longest-running transaction.
4. If you need to investigate further, check non-web transactions.

Non-web Transactions:

1. Go back to the Overview page and switch to Non-web transactions on the drop-down filter.
2. Review transaction traces at the bottom of the page, one by one.
3. Depending on the issue, use a third-party tool such as a PHP profiler to find a bottleneck.
4. If you need to investigate further, examine database processes.

Database processes:

1. On the APM page, go to Monitoring > Databases.

2. Sort by Most time-consuming.

3. Review TOP queries.

   Note: UPDATE or INSERT queries are the most CPU-consuming queries.

4. Switch to Throughput from the Sort by selector and look for processes that caused database throughput to drop-down.

5. If you need to investigate further, examine third-party services.

Third-party services:

1. On the APM page, go to Monitoring > External services.
2. Select Slowest average response time from the Sort by drop-down list.
3. Look for processes that occurred just before the outage.

To learn more about investigating specific performance problems, refer to New Relic Documentation > APM UI pages > Transactions page > Use drill-down functions.