Connection Details
| Section | Field | Description |
|---|---|---|
| Create New Collector | Database Type | The database type that you want to monitor. |
| Agent | The Database Agent that manages the collector. | |
| Collector Name | The name you want to identify the collector by. | |
| Connection Details | Hostname or IP Address | The hostname or IP address of the machine that your database is running on. |
| Listener Port | The TCP/IP address of the port on which your database communicates with the Database Agent | |
| Custom JDBC Connection String | The JDBC connection string generated by the database agent, for
example, jdbc:mysql:// . You can also specify a
custom connection string, which is useful for setting custom
authentication options. | |
| Database Credentials | Username | The name of the user who is connecting to and monitoring the database through the Database Agent. |
| Password | The password of the user who is connecting to and monitoring the database through the Database Agent. | |
| HashiCorp Vault | See Configure the HashiCorp Vault. | |
| Advanced Options | Sub-Collectors | Click to monitor multiple database instances in a
consolidated view, and aggregate metrics of multiple
databases. To monitor a custom cluster, you can add the
additional hostname or IP address, and port details for each
sub-collector. You can add up to a total of 29
sub-collectors. Thereby, 30 databases can be monitored in a
custom cluster. In addition to the licenses consumed by the
main collector, each sub-collector consumes one or more
licenses, depending on the database type.
Note:
|
| Connection Properties | Click to add a new JDBC connection property or edit an existing property for relational databases. | |
| Exclude Databases | The databases that you want to exclude, separated by commas. | |
| Monitor Operating System | See Configure the Database Agent to Monitor Server Hardware. |