To monitor Couchbase with Database Visibility, you must have:
- Couchbase >= 4.5
- Database Agent >= 20.x
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 | |
Username and Password | 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 Couchbase. |
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 website 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. | |
Advanced Options | SSL Connection | Click to enable SSL Connection:
If you also use client certificate authentication, then click the Enable SSL Client Authentication box.
You can set the context protocol for the SSL environment using the You can set the These platforms support TLSv1.3:
If a JDK version does not support TLSv1.3 or the specified context protocol, Splunk AppDynamics switches to TLSv1.2. |
Exclude Databases | The databases that you want to exclude, separated by commas. | |
Monitor Operating Systems | See Configure the Database Agent to Monitor Server Hardware. |
User Permissions for Couchbase
The monitoring user must have Full Administrator or Read-only Administrator privileges. Alternatively, if you do not want the monitoring user to have Administrator privileges, you can assign a combination of Data Monitoring and Query System Catalog privileges (available for Couchbase >= 5).