Documentation forDatabase Performance Analyzer

Register an Azure Database for MySQL or MariaDB

Complete the following steps to register an individual Azure Database for MySQL or MariaDB instance for monitoring with DPA.

You can use the registration wizard to register a read/write MySQL database instance. To register a read-only instance, see Monitor a read-only MySQL database instance in DPA.

To optimize DPA's reporting capabilities for an Azure Database for MySQL or MariaDB database instance, see the requirements for monitoring MySQL database instances.

You can also use mass registration to registrations to register multiple database instances, or you can register database instances using scripts that call the DPA API.

If you register a database instance within the 14-day trial period, DPA begins monitoring the instance immediately. After the trial period, you must activate a license to monitor the database instance.

Task 1: Create the monitoring user

Complete the following steps to create the user that DPA will use to monitor the database instance. Alternatively, you can specify an Azure AD Service Principal if you don’t want to create, manage, and update user credentials.

  1. Create the DPA monitoring user in Azure Database for MySQL. For more information, see Create users in Azure Database for MySQL in the Azure documentation.

  2. Run the following commands to grant the monitoring user the privileges required for monitoring:

    GRANT SELECT ON performance_schema.* TO 'dpa_user'@'%';

    GRANT UPDATE ON performance_schema.* TO 'dpa_user'@'%';

    GRANT PROCESS ON *.* TO 'dpa_user'@'%';

    GRANT SELECT ON *.* TO 'dpa_user'@'%';

  3. Run the following commands to grant the monitoring user the privileges required to enable the retrieval of query execution plans:

    GRANT INSERT ON *.* TO 'dpa_user'@'%';

    GRANT UPDATE ON *.* TO 'dpa_user'@'%';

    GRANT DELETE ON *.* TO 'dpa_user'@'%';

Task 2: Register the database instance

  1. In the upper-left corner of the DPA home page, click Register DB Instance for Monitoring.
  2. Under Microsoft Azure, select Azure Database for MySQL or MariaDB. Then click Next.

  3. On the Connection information panel, enter the host name or IP address of the database instance.

  4. Enter the port number.

  5. Under SSL mode, specify the type of secure socket layer (SSL) connections established between the instance and the DPA server.

    SSL mode Description
    Disable SSL encryption is not used.
    Require SSL is enabled, but no server certificate checks are performed. This SSL configuration does not protect against man-in-the-middle attack because no certificate is required.
    Verify-CA

    SSL is enabled. The client verifies that the server is trustworthy by checking the certificate chain up to a trusted certificate authority (CA).

    If you select this option and DPA cannot access a trusted certificate, you are prompted to import a certificate into the DPA trust store. Click the blue arrow to view certificate details.
    Verify-Identity

    SSL is enabled. The client verifies the certificate chain and also verifies that the server hostname matches its certificate's Subject Alternative Name or Common Name (CN).

    If you select this option and DPA cannot access a trusted certificate, you are prompted to import a certificate into the DPA trust store. Click the blue arrow to view certificate details.

  6. Enter the user name and password of the monitoring user created previously. Or, if DPA is configured to use CyberArk, enter the CyberArk credentials query for the monitoring user. Then click Next.

    DPA validates the connection information and the privileges of the monitoring user.

    DPA does not support connecting to the instance through a gateway.

  7. Specify the following Instance Options.

    The instance name and group membership can be changed after registration.

    1. Enter the name that DPA will display to identify this database instance.

      The Display name field defaults to the name retrieved from the database instance.

    2. (Optional) If you have manually created instance groups, you can assign this database instance to one of the groups.

      If no manual groups exist, this option is not shown.

    3. (Optional) If you have existing alert groups, you can assign this database instance to one or more groups.

      If no alert groups exist, or the existing groups do not match this instance's database type, this option is not shown.

    4. Click Next.

  8. Review the information on the Summary page. Click Back if you need to make changes. When the information is correct, click Register.

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.