Monitoring Apache CouchDB

eG Enterprise offers a special-purpose monitoring model for the Apache CouchDB to monitor the status and overall performance of the target Apache CouchDB server.

Figure 1 depicts the layer model of an Apache CouchDB server.

Figure 1 : Layer model for Apache CouchDB

Every layer in the Figure 1 is mapped to various tests to determine the critical statistics related to the performance of the target Apache CouchDB server. Using the metrics reported by the tests, administrators can find accurate answers for the following performance queries:

  • Is the cache for authentication process has been effectively utilized?

  • Is the running time of compaction greater than the configured running time?

  • Is there any storage space contentions on the database?

  • Is the compaction status is normal during last measurement period?

  • Is the cache for Design document has been effectively utilized or it needs any fine-tuning?

  • Is the rate at which writes operations performed on document is high?

  • Are there more attempts reported while reading the Data base file?

  • How well the HTTP Provider Service responds to the HTTP connection requests received from clients?

  • Is there any slowdown is detected due to server/web site unavailability and slow responses from the web site?

  • Is the running time of indexer greater than the configured running time?

  • Are there any abnormal conditions observed during the write, read and delete operations performed on the database during last measurement period?

  • Is the current size of the log files and their growth rate is abnormal?

  • Is there any erratic pattern of read repairs is reported in the background?

  • How many replications were currently running on the server?

  • Is there any document write operations that failed in the target environment as part of replication process?

  • Is there any consistent drop in the cache hits or any shared cache that were missed or totally evicted?

  • Are the databases were accessible in the target server?

  • Are there too many OS files are under open status in the databases of the target server?

  • Is the database server rebooted during the last measurement period?

  • Does the database server took maximum time since its last reboot?

Since the Operating System, Application Processes, Windows Service and TCP layers have been elaborately discussed in Monitoring Unix and Windows Servers document, and the tests mapped to the Network Layer have been elaborately discussed in Monitoring Cisco Router document, the sections to come will discuss the other layers in detail.