Managed alerts for ÃÛ¶¹ÊÓƵ Commerce: CPU warning alert
This article provides troubleshooting steps when you receive a CPU warning alert for ÃÛ¶¹ÊÓƵ 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.
Affected products and versions
ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure Pro plan architecture
Issue
You will receive an alert in New Relic if you have signed up to Managed alerts for ÃÛ¶¹ÊÓƵ Commerce and one or more of the alert thresholds have been surpassed. These alerts were developed by ÃÛ¶¹ÊÓƵ to give customers a standard set using insights from Support and Engineering.
Do!
- Abort any deployment scheduled until this alert is cleared.
- Put your site into maintenance mode immediately if your site is completely unresponsive. For steps, refer to Installation Guide > Enable or disable maintenance mode in our developer documentation. Make sure to add your IP to the exempt IP address list to ensure that you are still able to access your site for troubleshooting. For steps, refer to Maintain the list of exempt IP addresses in our developer documentation.
¶Ù´Ç²Ô’t!
- Launch additional marketing campaigns which may bring additional pageviews to your site.
- Run indexers or additional crons which may cause additional stress on CPU or disk.
- Do any major administrative tasks (i.e., Commerce Admin, data imports/exports).
- Clear your cache.
Solution
Follow these steps to identify and troubleshoot the cause.
-
Use to identify transactions with performance issues:
- Sort transactions by ascending Apdex scores. 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 .
- Sort transactions by highest throughput, slowest average response time, most time-consuming, and other thresholds. For steps, refer to New Relic .
-
If you are still struggling to identify the source, use to identify resource heavy services. For steps, refer to New Relic .
-
If you identify the source, SSH into the environment to investigate further. For steps, refer to Cloud for ÃÛ¶¹ÊÓƵ Commerce > SSH into your environment in our developer documentation.
-
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.
- Consider checking for and disabling flat catalogs. For steps, refer to Slow performance, slow and long running crons in our support knowledge base.
- If you suspect that you are experiencing a DDoS attack, try blocking bot traffic. For steps, refer to How to block malicious traffic for ÃÛ¶¹ÊÓƵ Commerce on Fastly level in our support knowledge base.
-
If the problem seems temporary, perform mitigation steps such as an upsize or place the site into maintenance mode. 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 ÃÛ¶¹ÊÓƵ 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. For steps, refer to Cloud for ÃÛ¶¹ÊÓƵ Commerce > Test Deployment > Load and stress testing in our developer documentation.