Logging is here!


Agent Check Agent Check


The Datadog Agent can collect many metrics from MySQL databases, including:

  • Query throughput
  • Query performance (average query run time, slow queries, etc)
  • Connections (currently open connections, aborted connections, errors, etc)
  • InnoDB (buffer pool metrics, etc)

And many more. You can also invent your own metrics using custom SQL queries.



The MySQL check is included in the Datadog Agent package, so simply install the Agent on your MySQL servers.


Create a mysql.yaml file in the Agent’s conf.d directory to connect it to the MySQL server.

Prepare MySQL

On each MySQL server, create a database user for the Datadog Agent:

mysql> CREATE USER 'datadog'@'localhost' IDENTIFIED BY '<UNIQUEPASSWORD>';
Query OK, 0 rows affected (0.00 sec)

Please note that @'localhost' is only for local connections, use the hostname/IP of your Agent for remote connections, learn more here

Verify that the user was created successfully using the following command, replacing <UNIQUEPASSWORD> with the password above:

mysql -u datadog --password=<UNIQUEPASSWORD> -e "show status" | \
grep Uptime && echo -e "\033[0;32mMySQL user - OK\033[0m" || \
echo -e "\033[0;31mCannot connect to MySQL\033[0m"
mysql -u datadog --password=<UNIQUEPASSWORD> -e "show slave status" && \
echo -e "\033[0;32mMySQL grant - OK\033[0m" || \
echo -e "\033[0;31mMissing REPLICATION CLIENT grant\033[0m"

The Agent needs a few privileges to collect metrics. Grant its user ONLY the following privileges:

Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> GRANT PROCESS ON *.* TO 'datadog'@'localhost';
Query OK, 0 rows affected (0.00 sec)

If the MySQL server has the performance_schema database enabled and you want to collect metrics from it, the Agent’s user needs one more GRANT. Check that performance_schema exists and run the GRANT if so:

mysql> show databases like 'performance_schema';
| Database (performance_schema) |
| performance_schema            |
1 row in set (0.00 sec)

mysql> GRANT SELECT ON performance_schema.* TO 'datadog'@'localhost';
Query OK, 0 rows affected (0.00 sec)

Metric Collection

  • Add this configuration setup to your mysql.yaml file to start gathering your MySQL metrics:

    - server:
      user: datadog
      pass: <YOUR_CHOSEN_PASSWORD> # from the CREATE USER step earlier
      port: <YOUR_MYSQL_PORT> # e.g. 3306
          replication: 0
          galera_cluster: 1
          extra_status_metrics: true
          extra_innodb_metrics: true
          extra_performance_metrics: true
          schema_size_metrics: false
          disable_innodb_metrics: false

In order to gather extra_performance_metrics, your MySQL server must have performance_schema enabled. Reference the MySQL documentation to enable it, otherwise set extra_performance_metrics to false. See our sample mysql.yaml for all available configuration options, including those for custom metrics.

The datadog user should be set up in the MySQL integration configuration as host: instead of localhost. Alternatively, you may also use sock.

Log Collection

Available for Agent >6.0

  1. By default MySQL logs everything in /var/log/syslog which requires root access to read. To change this and have specific files for MySQL logs follow these steps:

    • Edit /etc/mysql/conf.d/mysqld_safe_syslog.cnf and remove or comment the lines.
    • Edit /etc/mysql/my.cnf and add following lines to enable general, error and slow query logs:
    general_log = on
    general_log_file = /var/log/mysql/mysql.log
    slow_query_log = on
    slow_query_log_file = /var/log/mysql/mysql-slow.log
    long_query_time = 2
    • Save the file and restart MySQL using following commands: service mysql restart
    • Make sure the Agent has read access on those files (and the /var/log/mysql directory) and double check your logrotate configuration to make sure those files are taken into account and permissions are correctly set as well.
    • In /etc/logrotate.d/mysql-serverthere should be something similar to:
    /var/log/mysql.log /var/log/mysql/mysql.log /var/log/mysql/mysql-slow.log {
            rotate 7
            create 644 mysql adm
  2. Collecting logs is disabled by default in the Datadog Agent, you need to enable it in datadog.yaml:

    logs_enabled: true
  3. Add this configuration setup to your mysql.yaml file to start collecting your MySQL logs:

        - type: file
          path: /var/log/mysql/mysql_error.log
          source: mysql
          sourcecategory: database
          service: myapplication
        - type: file
          path: /var/log/mysql/mysql-slow.log
          source: mysql
          sourcecategory: database
          service: myapplication
        - type: file
          path: /var/log/mysql/mysql.log
          source: mysql
          sourcecategory: database
          service: myapplication
          # For multiline logs, if they start by the date with the format yyyy-mm-dd uncomment the following processing rule
          # log_processing_rules:
          #   - type: multi_line
          #     name: new_log_start_with_date
          #     pattern: \d{4}\-(0?[1-9]|1[012])\-(0?[1-9]|[12][0-9]|3[01])

    See our sample mysql.yaml for all available configuration options, including those for custom metrics.

  4. Restart the Agent.

Learn more about log collection on the log documentation


Run the Agent’s status subcommand and look for mysql under the Checks section:



    - instance #0 [OK]
    - Collected 168 metrics, 0 events & 1 service check



The MySQL integration is supported on versions x.x+

Data Collected


The current number of nodes in the Galera cluster.
shown as node
The number of free pages in the InnoDB Buffer Pool.
shown as page
The total number of pages in the InnoDB Buffer Pool.
shown as page
The number of used pages in the InnoDB Buffer Pool.
shown as page
The utilization of the InnoDB Buffer Pool.
shown as fraction
The number of current row locks.
shown as lock
The rate of data reads.
shown as read
The rate of data writes.
shown as write
The rate of mutex OS waits.
shown as event
The rate of mutex spin rounds.
shown as event
The rate of mutex spin waits.
shown as event
The rate of fsync writes to the log file.
shown as write
Fraction of time spent (ms/s) acquring row locks.
shown as fraction
The number of times per second a row lock had to be waited for.
shown as event
The rate of connections to the server.
shown as connection
The maximum number of connections that have been in use simultaneously since the server started.
shown as connection
The rate of delete statements.
shown as query
The rate of delete-multi statements.
shown as query
The rate of insert statements.
shown as query
The rate of insert-select statements.
shown as query
The rate of replace-select statements.
shown as query
The rate of select statements.
shown as query
The rate of update statements.
shown as query
The rate of update-multi.
shown as query
The rate of internal on-disk temporary tables created by second by the server while executing statements.
shown as table
The rate of temporary files created by second.
shown as file
The rate of internal temporary tables created by second by the server while executing statements.
shown as table
Percentage of CPU time spent in kernel space by MySQL.
shown as percent
The key cache utilization ratio.
shown as fraction
The number of open files.
shown as file
The number of of tables that are open.
shown as table
The rate of query cache hits.
shown as hit
The rate of statements executed by the server.
shown as query
The rate of slow queries.
shown as query
The total number of times that a request for a table lock could not be granted immediately and a wait was needed.
shown as
The number of currently open connections.
shown as connection
The number of threads that are not sleeping.
shown as thread
Percentage of CPU time spent in user space by MySQL.
shown as percent
The lag in seconds between the master and the slave.
shown as second
A boolean showing if this server is a replication slave that is connected to a replication master.
shown as
Number of slaves connected to a replication master.
shown as
The rate of queries.
shown as query

The check does not collect all metrics by default. Set the following boolean configuration options to true to enable its metrics:

extra_status_metrics adds the following metrics:

Metric name Metric type
mysql.binlog.cache_disk_use GAUGE
mysql.binlog.cache_use GAUGE
mysql.performance.handler_commit RATE
mysql.performance.handler_delete RATE
mysql.performance.handler_prepare RATE
mysql.performance.handler_read_first RATE
mysql.performance.handler_read_key RATE
mysql.performance.handler_read_next RATE
mysql.performance.handler_read_prev RATE
mysql.performance.handler_read_rnd RATE
mysql.performance.handler_read_rnd_next RATE
mysql.performance.handler_rollback RATE
mysql.performance.handler_update RATE
mysql.performance.handler_write RATE
mysql.performance.opened_tables RATE
mysql.performance.qcache_total_blocks GAUGE
mysql.performance.qcache_free_blocks GAUGE
mysql.performance.qcache_free_memory GAUGE
mysql.performance.qcache_not_cached RATE
mysql.performance.qcache_queries_in_cache GAUGE
mysql.performance.select_full_join RATE
mysql.performance.select_full_range_join RATE
mysql.performance.select_range RATE
mysql.performance.select_range_check RATE
mysql.performance.select_scan RATE
mysql.performance.sort_merge_passes RATE
mysql.performance.sort_range RATE
mysql.performance.sort_rows RATE
mysql.performance.sort_scan RATE
mysql.performance.table_locks_immediate GAUGE
mysql.performance.table_locks_immediate.rate RATE
mysql.performance.threads_cached GAUGE
mysql.performance.threads_created MONOTONIC

extra_innodb_metrics adds the following metrics:

Metric name Metric type
mysql.innodb.active_transactions GAUGE
mysql.innodb.buffer_pool_data GAUGE
mysql.innodb.buffer_pool_pages_data GAUGE
mysql.innodb.buffer_pool_pages_dirty GAUGE
mysql.innodb.buffer_pool_pages_flushed RATE
mysql.innodb.buffer_pool_pages_free GAUGE
mysql.innodb.buffer_pool_pages_total GAUGE
mysql.innodb.buffer_pool_read_ahead RATE
mysql.innodb.buffer_pool_read_ahead_evicted RATE
mysql.innodb.buffer_pool_read_ahead_rnd GAUGE
mysql.innodb.buffer_pool_wait_free MONOTONIC
mysql.innodb.buffer_pool_write_requests RATE
mysql.innodb.checkpoint_age GAUGE
mysql.innodb.current_transactions GAUGE
mysql.innodb.data_fsyncs RATE
mysql.innodb.data_pending_fsyncs GAUGE
mysql.innodb.data_pending_reads GAUGE
mysql.innodb.data_pending_writes GAUGE
mysql.innodb.data_read RATE
mysql.innodb.data_written RATE
mysql.innodb.dblwr_pages_written RATE
mysql.innodb.dblwr_writes RATE
mysql.innodb.hash_index_cells_total GAUGE
mysql.innodb.hash_index_cells_used GAUGE
mysql.innodb.history_list_length GAUGE
mysql.innodb.ibuf_free_list GAUGE
mysql.innodb.ibuf_merged RATE
mysql.innodb.ibuf_merged_delete_marks RATE
mysql.innodb.ibuf_merged_deletes RATE
mysql.innodb.ibuf_merged_inserts RATE
mysql.innodb.ibuf_merges RATE
mysql.innodb.ibuf_segment_size GAUGE
mysql.innodb.ibuf_size GAUGE
mysql.innodb.lock_structs RATE
mysql.innodb.locked_tables GAUGE
mysql.innodb.locked_transactions GAUGE
mysql.innodb.log_waits RATE
mysql.innodb.log_write_requests RATE
mysql.innodb.log_writes RATE
mysql.innodb.lsn_current RATE
mysql.innodb.lsn_flushed RATE
mysql.innodb.lsn_last_checkpoint RATE
mysql.innodb.mem_adaptive_hash GAUGE
mysql.innodb.mem_additional_pool GAUGE
mysql.innodb.mem_dictionary GAUGE
mysql.innodb.mem_file_system GAUGE
mysql.innodb.mem_lock_system GAUGE
mysql.innodb.mem_page_hash GAUGE
mysql.innodb.mem_recovery_system GAUGE
mysql.innodb.mem_thread_hash GAUGE
mysql.innodb.mem_total GAUGE
mysql.innodb.os_file_fsyncs RATE
mysql.innodb.os_file_reads RATE
mysql.innodb.os_file_writes RATE
mysql.innodb.os_log_pending_fsyncs GAUGE
mysql.innodb.os_log_pending_writes GAUGE
mysql.innodb.os_log_written RATE
mysql.innodb.pages_created RATE
mysql.innodb.pages_read RATE
mysql.innodb.pages_written RATE
mysql.innodb.pending_aio_log_ios GAUGE
mysql.innodb.pending_aio_sync_ios GAUGE
mysql.innodb.pending_buffer_pool_flushes GAUGE
mysql.innodb.pending_checkpoint_writes GAUGE
mysql.innodb.pending_ibuf_aio_reads GAUGE
mysql.innodb.pending_log_flushes GAUGE
mysql.innodb.pending_log_writes GAUGE
mysql.innodb.pending_normal_aio_reads GAUGE
mysql.innodb.pending_normal_aio_writes GAUGE
mysql.innodb.queries_inside GAUGE
mysql.innodb.queries_queued GAUGE
mysql.innodb.read_views GAUGE
mysql.innodb.rows_deleted RATE
mysql.innodb.rows_inserted RATE
mysql.innodb.rows_read RATE
mysql.innodb.rows_updated RATE
mysql.innodb.s_lock_os_waits RATE
mysql.innodb.s_lock_spin_rounds RATE
mysql.innodb.s_lock_spin_waits RATE
mysql.innodb.semaphore_wait_time GAUGE
mysql.innodb.semaphore_waits GAUGE
mysql.innodb.tables_in_use GAUGE
mysql.innodb.x_lock_os_waits RATE
mysql.innodb.x_lock_spin_rounds RATE
mysql.innodb.x_lock_spin_waits RATE

extra_performance_metrics adds the following metrics:

Metric name Metric type
mysql.performance.query_run_time.avg GAUGE
mysql.performance.digest_95th_percentile.avg_us GAUGE

schema_size_metrics adds the following metric:

Metric name Metric type
mysql.info.schema.size GAUGE


The MySQL check does not include any event at this time.

Service Checks


Returns CRITICAL for a slave that’s not running, otherwise OK.


Returns CRITICAL if the Agent cannot connect to MySQL to collect metrics, otherwise OK.


Further Reading

Read our series of blog posts about monitoring MySQL with Datadog.