MySQL metrics
Version 1.1.0 and above of the Amplify agent has a plugin for monitoring MySQL databases. Again, the agent should run in the same process environment as MySQL, and be able to find the mysqld processes with ps(1), otherwise the MySQL metric collection won't work.
The agent doesn't try to find and parse any existing MySQL configuration files. In order for the agent to connect to MySQL and collect the metrics, a few simple configuration steps should be performed.
To start monitoring MySQL, follow the instructions below.
Create a new user for the Amplify agent.
$ mysql -u root -p
[..]
mysql> CREATE USER 'amplify-agent'@'localhost' IDENTIFIED BY 'xxxxxx';
Query OK, 0 rows affected (0.01 sec)
Check that the user can read MySQL metrics.
$ mysql -u amplify-agent -p
..
mysql> show global status;
+-----------------------------------------------+--------------------------------------------------+
| Variable_name                                 | Value                                            |
+-----------------------------------------------+--------------------------------------------------+
| Aborted_clients                               | 0                                                |
..
| Uptime_since_flush_status                     | 1993                                             |
+-----------------------------------------------+--------------------------------------------------+
353 rows in set (0.01 sec)
Note. The agent doesn't use mysql(1) for metric collection, however it implements a similar query mechanism via a Python module.
Update the agent to the most recent version.
Add the following to /etc/amplify-agent/agent.conf
[extensions]
..
mysql = True

[mysql]
#host =
#port =
unix_socket = /var/run/mysqld/mysqld.sock
user = amplify-agent
password = xxxxxx
where the password option mirrors the password from the step #1 above.
Restart the agent.