Configuration of MySQLWorkLdTest

The error log contains a record of mysqld startup and shutdown times. It also contains diagnostic messages such as errors, warnings, and notes that occur during server startup and shutdown, and while the server is running. For example, if mysqld notices that a table needs to be automatically checked or repaired, it writes a message to the error log. Depending on error log configuration, error messages may also populate the Performance Schema error_log table, to provide an SQL interface to the log and enable its contents to be queried. If the error log grows abnormally or if the administrators notice a sudden/abnormal increase in the count of errors/warnings logged in the error log, the performance of the target database server instance may go in for a toss. To ensure smooth functioning of the database server, administrators need to periodically check for the errors/warnings logged in the error log and initiate pre-emptive measures to fix them. For this purpose, administrators can use the MySQLErrLogTesttest.

This test periodically monitors the error log of the target database server and reports the count of errors and warnings logged in the error log. This test also reports the total file size of the error log and the growth rate of the log file. Use the detailed diagnostics of this test to figure out when exactly were the errors/warnings noticed and what was the cause of such errors/warnings.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to choose how often should the test be executed.

• In the HOST text box, specify the IP address of the host for which the test is to be configured.

• In the PORT text box, specify the port at which the specified host listens.

• In the DATABASE text box specify the name of a database on the target MySQL database server being monitored.

• The eG agent has to be configured with the credentials of a user who has server-wide Process and Select privileges on the monitored MySQL server. Specify the credentials of such a user in the USERNAME and PASSWORD text boxes. To know how to create such a user, refer to Pre-requisites for Monitoring the MySQL Server topic in the Monitoring MySQL Server document.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• In the FILEPATH text box specify the full path to the error log file in the target MySQL database server instance. For example, in environments where the database server is installed on Linux, it can be: /var/log/mysql/error.log and in environments where the database server is installed on Microsoft Windows, it can be: C:/log/MySQL/error.log.

• If UTF-16 encoding is to be used for reading the specified log file, then, set the IsUTF16 flag to true. By default, this flag is set to false.

• The DETAILED DIAGNOSIS makes diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability

  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.