Couchbase Cluster Uptime Test

Couchbase cluster uptime refers to the total time the cluster remains fully operational and accessible without interruption. High uptime ensures continuous data availability, reliable performance, and minimal disruption to applications. It depends on stable node health, proper failover handling, and proactive monitoring of system resources and connectivity across the cluster.It is necessary to monitor the uptime of the critical database in the infrastructure. By tracking the uptime of a database, administrators can determine what percentage of time that database has been up. Comparing this value with service level targets, administrators can determine the most trouble-prone areas of the infrastructure.

In some environments, administrators may schedule periodic reboots of their database. By knowing that a specific database has been up for an unusually long time, an administrator may come to know that the scheduled reboot task is not working on a database. This test monitors the uptime of each node in the Couchbase Cluster.

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

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Has Couchbase server been restarted?	Indicates whether this node has been rebooted during the last measurement period or not.		The values reported by this measure and its numeric equivalents are mentioned in the table below: Measure Value Numeric Value No 0 Yes 1 Note: By default, this measure reports the Measure Values listed in the table above to indicate the current status of the node. The graph of this measure however, represents the status of the switch using the numeric equivalents only 0 to 1.
Uptime since last measure	Indicates the time that the database has been up since the last time this test ran.	Seconds	If the node has not been rebooted during the last measurement period and the agent has been running continuously, this value will be equal to the measurement period. If the node was rebooted during the last measurement period, this value will be less than the measurement period of the test. This measure value is calculated by the difference of previous uptime to current uptime status.
Uptime	Indicates the total time that the database has been up since its last reboot.	Minutes	This measure displays the number of years, months, days, hours, minutes, and seconds since the last reboot. Administrators may wish to be alerted if the database has been running without a reboot for a very long period. Setting a threshold for this metric allows administrators to determine such conditions.