Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA 11.1 Administrator Guide > Register a database instance for monitoring > Register a MySQL database

Register a MySQL database

Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Sep 15, 2016

Views: 76 Votes: 0 Revisions: 4

Updated: November 62017

To register a MySQL database for DPA to monitor:

  1. On the DPA homepage, click Register DB Instance for Monitoring.
  2. Under Self-Managed, click MySQL.
  3. Click Next.
  4. Complete the wizard panels as described in the following table.
Panel Instructions
Enter Monitored Database Instance Connection Information

Enter the host name or IP address and port of the server.

SolarWinds DPA monitors all databases within the instance. If more than one instance exists on the server, you must register each instance separately in DPA.

SolarWinds DPA ignores data generated by the monitoring user on the monitored database instance. For this reason, do not specify a user that causes load on the monitored instance. SolarWinds recommends creating a separate account for the monitoring user.

To create a new account:

  1. Click Provide a privileged user.
  2. Enter the credentials of an existing user with privileges to create the monitoring user and to grant the required permissions.

    The credentials for the privileged user are not used or stored after the registration.

    The privileged user requires the CREATE USER permission and must be able to grant the following permissions:

    PROCESS on *.*
    SELECT & UPDATE on performance_schema.*

    To enable the retrieval of query execution plans, this privileged user must be able to grant the following permissions:

    SELECT, INSERT, UPDATE, DELETE on *.*

  3. Enter credentials for the monitoring user. You can create a new user or use an existing one.

To specify an existing account:

  1. Click Provide the monitoring user.
  2. Enter credentials. DPA encrypts the password.

Alternatively, you can use the script that DPA provides to create a monitoring user.

  1. Click Monitoring User Creation Script, and follow the on-screen instructions.
  2. Copy the edited script to the MySQL console, and run it.
  3. Provide this user as your monitoring user.

SolarWinds DPA ignores data on the monitored database instance from the specified monitoring user. Make sure the monitoring user will not cause load on the monitored instance.

Oracle Repository Tablespace

If your repository database is not Oracle, the wizard skips this step.

Choose the tablespace in the repository database to store DPA performance data for this monitored instance.

By default, the performance data is stored in the default tablespace of the repository user. However, data for monitored instances can be stored in separate tablespaces.

Select the Alert Groups

If you have no Alert Groups set up, or if this new database instance does not match the database type of the Alert Group, the wizard skips this step.

Alert Groups simplify alert configuration and help make alerting more consistent across the monitored database instances.

Select the Alert Groups you want the new database instance to join.

MySQL Configuration for Monitoring

Select a Typical or Custom configuration. SolarWinds recommends the Typical configuration.

  • The DPA Recommended option is used for Performance Schema setup.
  • EXPLAIN can be run on SELECT statements.

Select Custom to change the Performance Schema setup and to allow EXPLAIN to be run on different statements.

Performance Schema setup

Specify what data the Performance Schema collects and maintains. This table shows which consumers and instruments each option enables.

The MySQL Performance Schema must be enabled. If you select Leave As Is, verify that Global Instrumentation and Thread Instrumentation are enabled in the existing Performance Schema configuration.

Option Server Default DPA Recommended Detailed Leave as Is
Consumer Global Instrumentation

NC

Consumer Thread Instrumentation

NC

Consumer Statement Digest

NC

Consumer Statement (Current)

NC

Consumer Wait (Current)   NC
Instrument Wait (Lock/*)   NC
Instrument Wait (I/O table) (I/O/file)   NC
Instrument Wait (I/O/socket)   NC
Instrument Wait (Synch/*)     NC
 

= Enabled.

NC = No change. DPA does not change the existing Performance Schema configuration.

* Values that are outside of the MYSQL_PERFORMANCE_SCHEMA configuration scope of DPA are not changed. For example, an instrument named stage exists in the MySQL Performance Schema. If you enable or disable that instrument, DPA will not change it.

Allow EXPLAIN to be run on

This section is displayed if you specified a privileged user to create the DPA monitoring user.

Select what type of statements you want DPA to collect execution plans for. The monitoring user can run EXPLAIN on the selected statement types.

Summary Review the information and click Register Database Instance.
Database Instance Registration Complete Click Finish to return to the DPA homepage.
Last modified

Tags

Classifications

Public