User Tools
Writing /app/www/public/data/meta/development/applications/prometheus-mysql-exporter.meta failed
development:applications:prometheus-mysql-exporter
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| development:applications:prometheus-mysql-exporter [2017/12/05 11:13] – adsilva | development:applications:prometheus-mysql-exporter [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Prometheus MySQL Exporter ====== | ||
| + | |||
| + | We use [[https:// | ||
| + | |||
| + | |||
| + | mysqld_exporter is a platform specific binary which must be deployed on the server where mysqld is running. It basically provides an HTTP endpoint with all the statistics related to the database. This end point is fetched/ | ||
| + | |||
| + | |||
| + | The set up is very straight forward. | ||
| + | |||
| + | Download the appropriate binary, usually mysqld_exporter-*.*.*.linux-amd64.tar.gz | ||
| + | |||
| + | uncompress the archive and set the environment variable as follows: | ||
| + | |||
| + | < | ||
| + | export DATA_SOURCE_NAME=' | ||
| + | </ | ||
| + | |||
| + | Then execute the binary: | ||
| + | < | ||
| + | ./ | ||
| + | </ | ||
| + | |||
| + | ====== Prometheus Configuration ====== | ||
| + | |||
| + | Once mysqld_exporter is running and it is confirmed that the endpoint is available, we can configure Prometheus as follows: | ||
| + | |||
| + | <code yaml> | ||
| + | - job_name: 'mysql performance' | ||
| + | scrape_interval: | ||
| + | static_configs: | ||
| + | - targets: | ||
| + | - ' | ||
| + | </ | ||
| + | |||
| + | **Note:** Due to Errigal' | ||
| + | |||
| + | |||
| + | Here is an extensive list of examples of rules that could be applied: [[https:// | ||
| + | |||
| + | For more information on how to setup your own rules in the Errigal environment, | ||
| + | refer: [[https:// | ||
Page Tools
