• /
  • EnglishEspañolFrançais日本語한국어Português
  • Log inStart now

Troubleshooting MySQL NRDOT monitoring

Preview

We're still working on this feature, but we'd love for you to try it out!

This feature is currently provided as part of a preview pursuant to our pre-release policies.

Troubleshoot common issues you may encounter when monitoring your MySQL with the NRDOT Collector.

Test connectivity

Test network connectivity to MySQL

First confirm the port is reachable at all:

bash
$
nc -zv <YOUR_DB_HOST> <YOUR_DB_PORT>

Then confirm the monitoring user can actually authenticate and query:

bash
$
mysql -h <YOUR_DB_HOST> -P <YOUR_DB_PORT> -u <YOUR_DB_USERNAME> -p -e "SELECT 1;"

If the command completes without an error, the monitoring user, host, and port are all correct.

Test OTLP endpoint connectivity

Run the following to verify your host can reach the selected New Relic OTLP endpoint:

bash
$
ENDPOINT="<YOUR_NEWRELIC_OTLP_ENDPOINT>"
$
HOST=$(echo "$ENDPOINT" | sed 's|https://||' | cut -d: -f1)
$
PORT=$(echo "$ENDPOINT" | awk -F: '{print $NF}')
$
(timeout 2 bash -c "</dev/tcp/$HOST/$PORT" && echo "SUCCESS") || echo "FAILED"

Expected output: SUCCESS

Common issues

NRQL query examples

Use these NRQL queries to troubleshoot and verify your MySQL monitoring:

Check for blocked queries

FROM Log SELECT * WHERE event.name = 'db.server.query_sample'
AND mysql.blocking.blocker.count > 0
SINCE 1 hour ago

Tip

Filter with mysql.blocking.blocker.count > 0, not != 0 — in NRQL, null != 0 evaluates to TRUE, which would silently include non-blocked sessions in your results.

Find slowest queries

FROM Log SELECT db.query.text,
mysql.events_statements_summary_by_digest.sum_timer_wait,
mysql.events_statements_summary_by_digest.count_star
WHERE event.name = 'db.server.top_query'
ORDER BY mysql.events_statements_summary_by_digest.sum_timer_wait DESC
LIMIT 10

Verify entity synthesis

FROM Metric SELECT uniqueCount(entity.guid)
WHERE metricName LIKE 'mysql.%'
FACET server.address, server.port
SINCE 1 hour ago

Getting help

If you continue experiencing issues:

  1. Check the NRDOT Collector logs:

    bash
    $
    journalctl -u nrdot-collector -f
  2. Verify your configuration syntax:

    bash
    $
    nrdot-collector validate --config=<your-config-file>
  3. Review our compatibility requirements

  4. Contact New Relic support with your collector logs and configuration (remove sensitive information like passwords)

Instrumentation in self-hosted environments

Learn how to set up MySQL monitoring in self-hosted environments with New Relic.

Instrumentation in RDS environments

Learn how to set up MySQL monitoring in RDS environments with New Relic.

Metrics reference

Learn about the available metrics collected by the NRDOT Collector.

Copyright © 2026 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.