eG Monitoring
 

Measures reported by CassLogTest

The Cassandra database logs are a vast source of information related to errors and warnings that a Cassandra database server encounters. Administrators use these log files not only to spot problem conditions, but also to troubleshoot them. By periodically scanning the Cassandra error log for errors/warnings, the CassLogTest test promptly notifies administrators as soon as a new error, warning, or fatal error is logged in the file.

As messages keep getting logged in the log files, these log files grow large in size. If log file growth is left unchecked, it can consume all available space in the database. Administrators can effectively track the log file growth and initiate measures to control it using the CassLogTest test. The test reports the errors logged in the log files, the current size of the log files and their growth rate, and proactively alerts administrators if the rate of growth is abnormal.

Ouputs of the test: One set of results for the target Cassandra Database node that is being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Error_count Indicates the number of error messages logged in the log files during the last measurement period. Number Ideally, the value of this measure should be 0.
Fatal_count Indicates the number of fatal errors captured by the log files during the last measurement period. Number Ideally, the value of this measure should be 0.
Warning_count Indicates the number of warning messages logged in the log files during the last measurement period. Number Ideally, the value of this measure should be 0.
File_size Indicates the current size of the log file. MB  
Growth_rate Indicates the rate at which the log file is growing. MB/sec A high value for this measure or a consistent increase in its value indicates that the Cassandra log is rapidly growing and may end up occupying too much space on the disk.