Agents Administration - Tests
 

Configuration of MySQLBlockerTest

The MySQLBlockerTest reports the number of root blockers in a database. The detailed diagnosis of this test, provides the details of each of these root blockers. The count and details of sessions blocked by these root blockers are also reported. The maximum time for which the sessions were blocked, and the details of the processes that were blocking them are also revealed.

The default parameters associated with this test are:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, specify the HOST for which this test is to be configured.

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

  • In the DATABASE, 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 BLOCKED SESSION COUNT text box, specify the minimum number of sessions a process should block for this test to count that process as a root blocker. For instance, if you specify 10 here, it indicates that the NumOfBlockers measure of this test will include only those processes that are blocking 10 or more sessions.

  • If a process is blocked for or beyond the duration (in seconds) specified in MAX BLOCKING TIME SECONDS, then this test will count that process as a process that has been blocked for a long time. eG Enterprise will then compare the blocked time of all such processes and determine the maximum blocking time. This maximum time value will be reported as the value of the MaxBlockingTime measure. Also, the detailed diagnosis of the NumOfBlockedSessions measure will list only those processes that were blocked for a period beyond the MAX BLOCKING TIME SECS configured. For example, if you specify 120 seconds here, then the detailed diagnosis of the MaxBlockingTime measure will display the details of all processes that were blocked for 2 minutes and above.

  • By default, SHOW EXPLAIN PLAN parameter is set to No indicating that the detailed diagnosis of this test will not list the detailed query plan of the root blockers. If you wish to view the detailed query plan for each root blocker reported by this test, then, set this flag to Yes.

  • By default, the target MySQL server being monitored is not SSL-enabled. This indicates that by default, the eG agent communicates with the MySQL server using HTTP. Accordingly, the SSL flag is set to No by default. If you configure the MySQL server to use SSL, then make sure that the SSL flag is set to Yes, so that the eG agent communicates with the MySQL server using HTTPS.

  • To make diagnosis more efficient and accurate, eG 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, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. 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 bad and normal 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 necessary values have been provided, clicking on the UPDATE button will 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.