Adding Targets Manually

You must configure a MySQL target that is monitored by Oracle Enterprise Manager.

Metrics are not collected until the MySQL database is added as a target.

Note:

When adding a MySQL database target, if the plugin is not deployed on the host selected, the system automatically deploys the plugin to the Management Agent on the target host.
  1. From the Setup menu, select Add Target, and select Add Targets Manually.
  2. In the Add Targets Manually page, click Add Target Manually on the Add Non-Host Targets Manually tile.
  3. In the Add Target Manually dialog, select the appropriate host and MySQL Database as the target type.
  4. Complete the following fields to configure and add the target:
    • Target Name: A unique name for the target. This value is displayed in the All Targets page.
    • MySQL User and Password: The credentials used to connect to the database. This should be the same user that connects to individual nodes.
    • Host: The host name of the MySQL database. This can be an IP address or a fully qualified name. If the database is local, you can specify localhost. Specify a value only if TCP/IP is the connection method used. Default host is localhost.
    • Port: The port used to connect to the database. Specify a value only if TCP/IP is the connection method used. Default port is 3306.
    • Socket: The socket used to connect to the database. Specify a value only if socket is the connection method used.
    • Kerberos KDC Server: Enter the Kerberos Key Distribution Center server only if Kerberos auth is being used. This assumes that the MySQL server has already been configured for Kerberos authentication.
    • Kerberos Realm: Enter the Kerberos Realm only if Kerberos auth is being used. This assumes that the MySQL server has already been configured for Kerberos authentication.
    • Use Secure: Choices are Require, No, or Yes. Entering Require enforces TLS and requires server certificate verification, else, the connection will fail. Entering No disables TLS and connects using plaintext. Entering Yes attempts to use TLS if available, but will silently fall back to an unencrypted connection if TLS cannot be established. Certificate verification is not enforced when the value is Yes and thus, is not recommended for production use.
    • Client Truststore Path: Path to the truststore. Only required if using secure communication and if not using the OMA's default java truststore.
    • Client Truststore Type: JKS or PKCS12. Only required if using secure communication and if not using the OMA's default java truststore.
    • Client Truststore Password: The password required to access the truststore. Only required if using secure communication and if not using the OMA's default java truststore or if the truststore's password has been modified from the default password.
  5. Click OK to save the target.
  6. Click Targets and select All Targets to return to the All Targets page.

    The new target is displayed as MySQL Database in the Databases Target Type.

    Note:

    Do not attempt to access the new target until a green arrow is displayed for the new target in the Target Status column.

    It is also possible to monitor a remote MySQL database without deploying an agent or plugin to that host. To remotely monitor a MySQL database, repeat these steps with an existing agent and, on the Add MySQL Database page, add the details for the remote database.

    Remote monitoring does not allow monitoring of the host machine, only of the MySQL database running on that host.

Adding the InnoDB Cluster Target Manually

Note:

Before setting up the cluster target, ensure that you have already added its individual nodes as database targets to the same Oracle Enterprise Manager environment.
  1. From the Setup menu, select Add Target, and select Add Targets Manually.
  2. In the Add Targets Manually page, click Add Target Manually on the Add Non-Host Targets Manually tile.
  3. In the Add Target Manually dialog, select the appropriate host and MySQL InnoDB Cluster as the target type.
  4. Complete the following fields to configure and add the target:
    • Target Name: A unique name for the target. This value is displayed in the All Targets page.
    • MySQL User and Password: The credentials used to connect to the database. This should be the same user that connects to individual nodes.
    • Host: The host name of the MySQL server or router.
    • Port: The port of the MySQL server or router. It is recommended to use a router/proxy port for a cluster target. Connecting directly to a node's port is possible, however, metrics will reflect that node's current role, which may change during failover.
    • Socket: The socket used to connect to the database. This is optional and should only be specified if a socket connection is needed.
    • Kerberos KDC Server: Enter the Kerberos Key Distribution Center server only if Kerberos auth is being used. This assumes that the MySQL server has already been configured for Kerberos authentication.
    • Kerberos Realm: Enter the Kerberos Realm only if Kerberos auth is being used. This assumes that the MySQL server has already been configured for Kerberos authentication.
    • Use Secure: Choices are Require, No, or Yes. Entering Require enforces TLS and requires server certificate verification, else, the connection will fail. Entering No disables TLS and connects using plaintext. Entering Yes attempts to use TLS if available, but will silently fall back to an unencrypted connection if TLS cannot be established. Certificate verification is not enforced when the value is Yes and thus, is not recommended for production use.
    • Client Truststore Path: Path to the truststore. Only required if using secure communication and if not using the OMA's default java truststore.
    • Client Truststore Type: JKS or PKCS12. Only required if using secure communication and if not using the OMA's default java truststore.
    • Client Truststore Password: The password required to access the truststore. Only required if using secure communication and if not using the OMA's default java truststore or if the truststore's password has been modified from the default password.
In about 15-30 minutes the initial metric collections should begin. Note that this can take longer if the individual node targets have only recently been added.