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. To monitor a cluster, specify the hostname or IP address of the listener of the cluster. See Monitor the Microsoft SQL Server Cluster to enable monitoring the MSSQL cluster.
	Listener Port	The TCP/IP address of the port on which your database communicates with the Database Agent. If you are using a Microsoft SQL Server cluster, specify the listener port of the cluster. To enable monitoring of all the nodes in a cluster, you must enable the monitoring of the cluster. This allows the agent to automatically discover all the nodes present in a cluster. See Monitor the Microsoft SQL Server Cluster.
	Windows Authentication	Click to enable Windows authentication when connecting to the database.
	Custom JDBC Connection String	The JDBC connection string generated by the database agent, for example, `jdbc:sqlserver://`. 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. The user should have the permissions described in User Permissions for Microsoft SQL Server.
	Password	The password of the user who is connecting to and monitoring the database through the Database Agent.
	CyberArk	Click to enable CyberArk for database username and password. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. To use CyberArk with Database Visibility, you must download the `JavaPasswordSDK.jar` file from the CyberArk web site and rename the file to `cyberark-sdk-9.5.jar`. Then, you must copy the JAR file to the `lib` directory of the database agent zip file.
	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 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: All connection parameters other than the hostname or IP address, and port details of the sub-collector are the same as the main collector. If you want to specify different parameters for the sub–collectors, while creating or editing the collector configuration, you can do that only via the Create Collector API. You cannot convert a custom cluster collector to a standalone collector. If you want to monitor a standalone database, delete the entire custom cluster collector and create a fresh standalone collector. However, note that deleting the custom cluster collector will delete all its historical data.
	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 Systems	See Configure the Database Agent to Monitor Server Hardware.

Note: By default, Database Agent uses TLSv1.1 for SSL connections. To prevent any SSL version error in the SQL server 2019 and later versions, set the sslProtocol to TLSv1.2 or TLSv1.3 (whichever is supported) by adding any one of the following connection parameters:

"sslProtocol=TLSv1.2"

"sslProtocol=TLSv1.3"

Note: To handle High Availability (Multi-AZ) for Amazon RDS, set the database Name JDBC connection string property to a user database.

Documentation

Connection Details