- Metricbeat Reference: other versions:
- Overview
- Contributing to Beats
- Getting started with Metricbeat
- Setting up and running Metricbeat
- Upgrading Metricbeat
- How Metricbeat works
- Configuring Metricbeat
- Specify which modules to run
- Specify general settings
- Load external configuration files
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and enhance the exported data
- Parse logs by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Set up logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- metricbeat.reference.yml
- Modules
- Aerospike module
- Apache module
- Ceph module
- Couchbase module
- Docker module
- Dropwizard module
- Elasticsearch module
- Golang module
- HAProxy module
- HTTP module
- Jolokia module
- Kafka module
- Kibana module
- Kubernetes module
- Kubernetes container metricset
- Kubernetes event metricset
- Kubernetes node metricset
- Kubernetes pod metricset
- Kubernetes state_container metricset
- Kubernetes state_deployment metricset
- Kubernetes state_node metricset
- Kubernetes state_pod metricset
- Kubernetes state_replicaset metricset
- Kubernetes system metricset
- Kubernetes volume metricset
- Memcached module
- MongoDB module
- MySQL module
- Nginx module
- PHP-FPM module
- PostgreSQL Module
- Prometheus module
- RabbitMQ module
- Redis module
- System module
- vSphere module
- Windows module
- ZooKeeper module
- Exported Fields
- Aerospike Fields
- Apache Fields
- Beat Fields
- Ceph Fields
- Cloud Provider Metadata Fields
- Common Fields
- Couchbase Fields
- docker Fields
- Docker Fields
- Dropwizard Fields
- Elasticsearch Fields
- Golang Fields
- HAProxy Fields
- HTTP Fields
- Jolokia Fields
- Kafka Fields
- Kibana Fields
- kubernetes Fields
- Kubernetes Fields
- Memcached Fields
- MongoDB Fields
- MySQL Fields
- Nginx Fields
- PHP-FPM Fields
- PostgreSQL Fields
- Prometheus Fields
- RabbitMQ Fields
- Redis Fields
- System Fields
- vSphere Fields
- Windows Fields
- ZooKeeper Fields
- Securing Metricbeat
- Troubleshooting
WARNING: Version 6.0 of Metricbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
MySQL module
editMySQL module
editThis module periodically fetches metrics from MySQL servers.
Module-specific configuration notes
editWhen configuring the hosts
option, you must use a MySQL Data Source Name (DSN)
of the following format:
[username[:password]@][protocol[(address)]]/
You can also separately specify the username and password using the respective
configuration options. Usernames and passwords specified in the DSN take
precedence over those specified in the username
and password
config options.
- module: mysql metricsets: ["status"] hosts: ["tcp(127.0.0.1:3306)/"] username: root password: secret
Compatibility
editThe mysql MetricSets were tested with mysql 5.7.12 and are expected to work with all versions >= 5.7.0.
Example configuration
editThe MySQL module supports the standard configuration options that are described in Specify which modules to run. Here is an example configuration:
metricbeat.modules: - module: mysql metricsets: ["status"] period: 10s # Host DSN should be defined as "user:pass@tcp(127.0.0.1:3306)/" # The username and password can either be set in the DSN or using the username # and password config options. Those specified in the DSN take precedence. hosts: ["root:secret@tcp(127.0.0.1:3306)/"] # Username of hosts. Empty by default. #username: root # Password of hosts. Empty by default. #password: secret # By setting raw to true, all raw fields from the status metricset will be added to the event. #raw: false
Metricsets
editThe following metricsets are available: