Couchbase Cluster Connectivity Test

Couchbase cluster connectivity refers to how nodes within the cluster communicate with each other and with clients. It requires stable network links for inter-node data replication, rebalance, and service coordination. Clients must connect to all relevant nodes, not just, to access distributed services reliably. Proper firewall, port configurations, and DNS resolution are essential for maintaining seamless connectivity.

Monitoring cluster connectivity is vital to detect node communication issues, prevent data replication failures, and ensure service availability. Connectivity problems can lead to inconsistent data, failed queries, or node isolation, affecting application performance and overall cluster health.

This test reports the availability and responsiveness of each node in the cluster, collects statistics pertaining to the query execution time on each node.

Target of the test : Couchbase Cluster

Agent deploying the test : An external agent

Outputs of the test : One set of results for the target Couchbase Cluster

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The IP address of the Couchbase database server.
Port	The port on which the server is listening.
Username	To monitor a Couchbase server, a special database user account with Admin privilege must be created in every Couchbase server instance that requires monitoring. In the Username text box, specify the Username for monitoring the target Couchbase server instance.
Password	Specify the password for the username in Password textbox.
Confirm Password	Confirm the password by typing it in Confirm Password textbox.
Available nodes	In the Available Nodes text box, provide a comma-separated list of all the available nodes to be included for monitoring. This way, the test monitor and collect metrics from all the available nodes in the cluster. By default, this parameter is set to none. The format of this configuration is: HOSTNAME:PORT, for example, 172.16.14.147:8091,172.16.15.67:8091
Query	Specify the SQL++ 'select' query to execute. The default is "select name from system:buckets".
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Database connection availability	Indicates whether the database connection to this node is available or not.	Percent	If this measure reports the value is 100. It indicates the database connection is available. The value is 0 on the other hand indicates that the database connection is unavailable. A connection to the database may be unavailable if the database is down or if the database is listening on a port other than one configured for it in the eG manager or owing to poor network link. If this measure reports the value 0, then, you can check the value of this measure to determine whether/not it is due to the unavailability of a connection to the server.
Database connection response time	Indicates the time taken by the database connection.	Seconds	A high value could indicate a connection bottleneck. Whenever the total response time of the measure soars, you may want to check the value of this measure to determine whether a connection latency is causing the poor responsiveness of the server.
Query processor availability	Indicates whether the query to this database is executed successfully or not.	Percent	If this measure reports the value of 100, it indicates that the query was executed successfully. The value 0 on the other hand indicates that the query failed. Check whether the node hosting the query service is up or down. If it is down, the query fails.
Query execution time	Indicates the time taken for query execution.	Seconds	A high value could indicate that one/more queries to the database are taking too long to execute. Inefficient/badly designed queries to the database often take too long to execute. If the value of this measure is higher than that of the connection time measures, the respond slowly to requests.
No of records	Indicates the number of records fetched from the database.	Seconds	The value 0 indicates that no records are fetched from the database.
Average response time	Indicates the average time taken by the cluster to respond to a query.	Seconds	A sudden increase in response time is indicative of a potential performance bottleneck on the database cluster.