This article provides troubleshooting steps for when you receive a Redis memory critical alert for Adobe Commerce in New Relic. Immediate action is required to resolve 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 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 to give merchants a standard set of alerts using insights from Support and Engineering.
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, refer to 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:
If no support ticket exists, check if Redis Used Memory is increasing or decreasing by going to one.newrelic.com > Infrastructure > Third-party services page, select the Redis dashboard. If it is stable or increasing, submit a support ticket to have your cluster upsized, or increase the
maxmemory limit to the next level.
If you cannot identify the cause of increased Redis 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.
Check for misbehaving third party extensions:
If there is no evidence of misbehaving extensions, Install latest patches to fix Redis issues for Adobe Commerce on cloud infrastructure.
If the above steps do not help you identify or troubleshoot the source of the issue, consider enabling L2 cache to reduce network traffic between the app and Redis. For general information on what is L2 cache, refer to L2 caching in the Adobe Commerce application in our developer documentation. To enable L2 cache for cloud infrastructure, try the following:
stage: deploy: REDIS_BACKEND: '\Magento\Framework\Cache\Backend\RemoteSynchronizedCache'