The MySQL error log is quintessential in determining the health of the server. You can Enable error log monitoring to allow SQL DM for MySQL to keep an eye on your MySQL Error Log and notify you of important information. 

Enable error log monitoring:

Select the toggle switch to Enable error log monitoring.

Read file from:

There are 3 ways of accessing the log files: Select "Local path" if the logs are in the machine where SQL DM for MySQL is running, or if they can be accessed by SQL DM for MySQL on a shared network drive. Choose "Via SFTP" if you have configured SQL DM for MySQL to use SSH. Select "RDS/Aurora (Using API)" if your server is a RDS/Aurora instance. In case of RDS/Aurora (Using API) for file based logging, four additional fields have to be filled, which are:

• DB instance identifier: A unique name to identify your RDS/Aurora instance.
• Instance region: The region in which your instance is hosted, for e.g: us-east-1
• Access key ID: It is a 20 character long key ID which can be created from the AWS Management console. It is used to make programmatic request to AWS.
• Secret access key: It is 40 character long and can be created from the AWS Management console. You can refer to the documentation, on how to generate credential keys here: .

Fetch error log details:

SQL DM for MySQL can automatically get the path of the error log from the MySQL server. Just click the fetch button, and SQL DM for MySQL will do the rest for you.

File path:

If you choose to enter the error log file path manually, you may do so here.

Test path:

Click this button to check if SQL DM for MySQL can access the file specified in the File path.