Page History
...
Use this option to Auto register all the Galera nodes of your cluster with SQL DM for MySQL. The MySQL and the SSH details of the nodes are assumed to be the same as that of the node on which you are enabling this option. In case the other node details are different from that of the node on which you are enabling this option, you will have need to manually go edit that server and change details. You can do a “Test” to check if SQL DM for MySQL is able to connect to the other nodes. If the “Test” gives a successful message then you can go ahead and click on “Save”. SQL DM for MySQL will then register the detected nodes and redirect you will be redirected to the Servers page where you can see all the registered nodes.
...
SQL DM for MySQL can automatically get the path of the error log from the MySQL server. Just click on the fetch button, and SQL DM for MySQL will do the rest for you.
...
If you choose to enter the error log file path manually, you may do so here.
Test path:
Click on this button to check if SQL DM for MySQL can access the file specified in the File path.
...
SQL DM for MySQL retrieves (completely or partially) the General query log and the Slow query log from the MySQL servers it connects to, and analyzes them. Here, we will see how to set up details for the connection, so that log analysis will be is available with SQL DM for MySQL. You will have to set up details for the general query log and the slow query log independently. Enabling slow query log 'log queries not using indexes' instead needs SUPER privilege. Refer to the MySQL documentation on how to enable and configure logging. MySQL server logs can be written to files on the server machine or to tables in the MySQL database itself.
...
Logs written to files:
First, we will lets consider the situation where server logs are stored as files on the server machine. This is the most common situation and the only one available with MySQL servers before version 5.1. First time you configure a server with this option you should , click the 'Fetch query log details' button. The MySQL server 'knows' (it is stored in server variables) what logs are enabled and how logging is configured. Click 'Test Path' to verify that the path . SQL DM for MySQL will connect and verify the existence of the file (but not its content).
The log files can be accessed from the local file system (if SQL DM for MySQL and MySQL is running on the same computer) or by using SFTP (if SQL DM for MySQL and MySQL is running on different computers) or by using RDS/Aurora (Using API) if you are using a RDS/Aurora instance. You should note Note that you must use the file and path syntax of the machine where the logs are.
If the log files can be accessed from a shared drive, over a network, or from a network enabled file system (like NFS on Linux), then SQL DM for MySQL can access them as if they were local files. No additional SSH/SFTP configuration is required in this case: the operating system will take takes care of the file transfer transparently.
...