12.4 MySQL Instances

This page is for viewing and controlling the MySQL instances that are being monitored by MySQL Enterprise Monitor, and configuring MySQL instances to be monitored.

Figure 12.3 MySQL Instances: Overview

MySQL Instances: Overview

Note

Keep in mind that the Status Summary at the top right of MySQL Enterprise Monitor User Interface is directly related with the information shown on the MySQL Instances page.

General Instance Control

This section contains three buttons that let you:

Note

Connections for every Agent may be configured from this dashboard, when the Agent is installed with the Installer, or with the agent.sh script that is bundled with each Agent.

Figure 12.4 MySQL Instances: Add MySQL Instance

MySQL Instances: Add MySQL Instance

Figure 12.5 MySQL Instances: Add Bulk MySQL Instances

MySQL Instances: Add Bulk MySQL Instances

Unmonitored MySQL Instances

The unmonitored MySQL instances section is only shown when both the MySQL Process Discovery advisor is active, and there are unmonitored MySQL instances that where detected by this advisor.

This feature needs to know the port number, basedir, and datadir to know that a connected MySQL server matches one that is unmonitored. The mysqld does not return enough information to do this any other way, so essentially unmonitored MySQL instances are found if MySQL is started by mysqld_safe or similar.

Note

A MySQL instance will be seen as "unmonitored" if a local Agent discovers a MySQL instance that it is not monitoring. This MySQL instance could be seen as both monitored and unmonitored if a different Agent is monitoring it, or if it is being monitored remotely.

A workaround is to override the Advisor to not to perform process discoveries.

From the list of unmonitored connections, you can:

  • Monitor Instance: Only used on processes that are not currently attempting a connection. This opens the Add MySQL Instance menu, with pre-populated data filled in from the discovery process.

  • Cancel Pending Connection: Can only be used for connections that are currently being attempted, but were not yet completed. This will effectively cancel the attempt to establish a connection to that instance.

Note

After adding a connection to an unmonitored process, the MySQL instance may appear as both unmonitored and monitored for a brief moment of time.

Figure 12.6 MySQL Instances: Cancel Pending Connections

MySQL Instances: Cancel Pending Connections

You can perform Monitor Instance and Cancel Pending Connection actions on a single discovered instance, or when configuring multiple (bulk) instances.

When you are monitoring multiple discovered processes in a bulk operation, the menu will not show an Agent selection, nor will it show information for the connection itself. In other words, it will only show the credentials as seen in the screenshot below. Both the Agent and the connection details will automatically be selected on a per-instance basis based on the information extracted from the discovered process. The defined credentials are used for every instance of the bulk operation:

Figure 12.7 MySQL Instances: Adding Multiple Discovered Processes

MySQL Instances: Adding Multiple Discovered Processes

Bad Connections

The bad connections section is displayed if there are bad connections to the monitored MySQL instances. Possible scenarios that cause bad connections are:

  • A connection that was created with the wrong credentials.

  • A connection that was issued to an unknown host.

  • Any connection that could not be established.

You can get more detailed information on the error that caused the bad connection by hovering your mouse over it:

Figure 12.8 MySQL Instances: Bad Connection Error

MySQL Instances: Bad Connection Error

Note

Usually a bad connection means that MySQL Enterprise Monitor cannot find any monitoring data from the MySQL instance, as MySQL Enterprise Monitor cannot access the instance, but this is not always true. For example, for a connection that is using less privileged users, the administrator credentials may be correct while the less privileged credentials may be wrong. In this scenario we could still monitor the server using the administrator connection while showing the bad connection for the less privileged users.

The screenshot below shows that a MySQL instance connection to 127.0.0.1:5168 is showing as a bad connection, but also notice that the MySQL instance is still being listed as correctly monitored.

The MySQL instance displays the name and port number, or socket name, with which it was initially configured.

Figure 12.9 MySQL Instances: A connection showing up as bad and good

MySQL Instances: A connection showing up as bad and good

The bad connections table enables you to access the context menu for each of the bad connections, which contains the following:

Note

2.x Agent connections cannot be edited from this interface.

  • Edit Connection: Generates a window to edit the connection details.

  • Delete Connection: Removes the connection. If you delete the connection, it is not longer displayed as a bad connection, and is forgotten by MySQL Enterprise Service Manager.

    Note

    If you remove a bad connection but the MySQL instance is still running and detectable, the unmonitored instance is displayed highlighted in red on the instances list:

Figure 12.10 MySQL Instances: No Connection

MySQL Instances: No Connection

For each bad connection, MySQL Enterprise Service Manager attempts to establish the connection for a fixed period of time (this connection timeout defaults to 5 minutes). After the timeout, MySQL Enterprise Service Manager stops attempting to establish the connection, and the connection is shown as a bad connection:

Figure 12.11 MySQL Instances: Connection timeout

MySQL Instances: Connection timeout

Unreachable Agents

The Unreachable Agents section displays information about the unreachable Agents, and provides a Delete Agent action.

This section is only visible if there are unreachable Agents

MySQL Instance Details

The MySQL Instance Details section shows the list of monitored instances. From this section you can:

Note

Remotely monitored hosts and 2.3 Agents are highlighted with a caution icon ( A caution icon ). Hover over this icon and review the suggested change.

  • Filter: This searches through the specific instances using keywords.

  • Delete Instance: This will remove this instance from the list of MySQL Enterprise Monitor's monitored instances.

  • Edit Instance: Allows you to edit any information concerning that instance.

  • Export Overview as CSV: Exports the list of monitored instances as a comma-separated values (CSV) file.

  • Control Groups: Accessed from the context menu on the group.

    • Add to Group: Adds a MySQL instance to the group.

    • Delete Group: Removes the group (the instances within the group will not be removed, but will be dissociated from the removed group).

    • Rename Group: Renames the group.

      Note

      The text is captured as is in the text field. For example, HTML entities are not converted.

    • Support Diagnostics: Opens the Support Diagnostics page. This enables you to generate a set of reports which you can send to MySQL Support as an attachment to a reported issue. This report can take several minutes to generate. The reports archive also includes a SQL dump of the Advisor Schedules, Inventory and Configuration schemas.

      Important

      The Configuration schema may contain login credentials. However, these credentials are encrypted using keys which are not stored in the repository and are not included in the Support Diagnostics report.

Figure 12.12 MySQL Instances: Group Context Menu

MySQL Instances: Group Context Menu

You can execute the Delete Instance and Edit Instance actions on a single instance, or on multiple instances using the bulk operation. When editing multiple instances, the same logic used for monitoring instances applies.