۶Ƶ

DocumentationCommerceCommerce KB

Managed alerts on ۶Ƶ Commerce: MariaDB alerts

Last update: Wed Nov 06 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin

This article provides troubleshooting steps when you receive MariaDB alerts for ۶Ƶ Commerce in New Relic. The MariaDB alerts monitor high query load as well as excessive Data Manipulation Language (DML) queries. Both can lead to a degraded user experience or even downtime. You can receive four kinds of alerts:

  • DML Queries Warning
  • DML Queries Critical

Affected products and versions

۶Ƶ Commerce on cloud infrastructure Pro plan architecture

Issue

You will receive a managed 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 or becomes 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.
  • End any scripts such as imports that may be the cause of the alert if site performance is impacted.

ٴDz’t!

  • Run indexers or additional crons which may cause additional stress on MariaDB.
  • Do any major administrative tasks (i.e., Commerce Admin, data imports / exports).
  • Clear your cache.

Solution

DML Queries (queries that modify the database using UPDATE, INSERT, and DELETE)

If you receive a DML Queries Critical alert start at step one. If you receive a DML Queries Warning alert start at step two.

  1. Check if an ۶Ƶ Commerce support ticket exists. For steps, refer to our knowledge base Track your support tickets. Support may have 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:
  2. Contact Reason: select “New Relic MariaDB alert received”.
  3. Description of the alert.
  4. . This is included in your Managed alerts for ۶Ƶ Commerce.
  5. To identify the source of the issue, try to identify the DML queries:
  6. Review your database operations by using steps from New Relic .
  7. Sort by CALL COUNT, then OPERATION. Review INSERT, DELETE, and UPDATE operations.
  8. Look for high AVG.
  9. Click through to find database operation callers. This will identify transactions using that query by time.
  10. Seek out either code optimizations, or operational optimizations:
  11. Code optimizations: Look to optimize queries with bulk inserts / updates, minimizing index usage, or throttling code.
  12. Operational optimizations: Offload resource intensive data modifications to lower traffic times.
  13. Additional optimizations: Ensure that you are on the latest version of ECE-Tools. For steps, refer to Cloud for ۶Ƶ Commerce > Update ece-tools version in our developer documentation.
recommendation-more-help
8bd06ef0-b3d5-4137-b74e-d7b00485808a