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 Adobe 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. New Relic Incident link. This is included in your Managed alerts for Adobe 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 APM UI Pages > Monitoring > Databases page .
  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 Adobe Commerce > Update ece-tools version in our developer documentation.
Previous pageManaged alerts for Adobe Commerce: Apdex critical alert
Next pageManaged alerts for Adobe Commerce: Apdex 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