CouchDB Uptime Test
In most production environments, it is essential to monitor the uptime of critical servers in the infrastructure. By tracking the uptime of each of the servers, administrators can determine what percentage of time a server 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 servers. By knowing that a specific server has been up for an unusually long time, an administrator may come to know that the scheduled reboot task is not working on a server.
This test included in the eG agent monitors the uptime of the target Apache CouchDB server.
Target of the test : Apache CouchDB Server
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for the target Apache CouchDB Server.
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed. |
|
Host |
The IP address of the target server that is being monitored. |
|
Port |
The port number through which the Couchdb server communicates. The default port is 5984. |
|
Username |
In order to monitor an Apache CouchDB server, a special database user account with Admin privilege has to be created in every Apache CouchDB server instance that requires monitoring. In the Username text box, specify the Username for monitoring the target Apache CouchDB server instance.To create a new user, refer Pre-requisites for Monitoring Apache CouchDB topic. |
|
Password |
Specify the password of the specified Username. |
|
Confirm Password |
Confirm the password by retyping it here. |
|
Report Manager Time |
By default, this flag is set to Yes, indicating that, by default, the detailed diagnosis of this test, if enabled, will report the shutdown and reboot times of the server in the manager’s time zone. If this flag is set to No, then the shutdown and reboot times are shown in the time zone of the system where the agent is running (i.e., the system on which the remote agent is running - for agentless monitoring). |
|
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time the test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency. |
|
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:
|
| Measurement | Description | Measurement Unit | Interpretation | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
Uptime |
Indicates the total time that the database server 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 server has been running without a reboot for a very long period. Setting a threshold for this metric allows administrators to determine such conditions. |
||||||
|
Uptime since last measure |
Indicates the time period that the database server has been up since the last time this test ran. |
Seconds |
If the database server 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 database server was rebooted during the last measurement period, this value will be less than the measurement period of the test. For example, if the measurement period is 300 secs, and if the database server was rebooted 120 secs back, this metric will report a value of 120 seconds. The accuracy of this metric is dependent on the measurement period ? the smaller the measurement period, greater the accuracy. |
||||||
|
Is rebooted? |
Indicates whether the database server 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:
Note: By default, this measure reports the Measure Values listed in the table above to indicate whether the database server has been rebooted during the last measurement period or not. If the value of this measure is 1, it means that the database server was rebooted during the last measurement period. By checking the time periods when this metric changes from 0 to 1, an administrator can determine the times when this database server was rebooted. Use the detailed diagnosis of this measure to figure out the Time, Shutdown Date, Restart Date, Shutdown Duration, and Is Maintenance details. |
