Cassandra Storage Test

This test reports the current size of the target Cassandra Database node and the rate at which data is growing. This test also reveals the rate of unhandled exceptions on the database node. Using this test, administrators can figure out how well the database node is growing as well as capture and rectify the unhandled exceptions before the data becomes stale!

Target of the test : A Cassandra Database

Agent deploying the test : An external/remote agent

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

Configurable parameters for the test
Parameters Description

Test Period

How often should the test be executed.


The host for which the test is to be configured.


The port on which the specified host listens. By default, this is 9042.

JMX Remote Port

Here, specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the file (if the target Cassandra Database node is installed on a Unix host) or the cassandra-env.ps1 file (if the target Cassandra Database node is installed on a Windows host) in the <CASSANDRA_HOME> directory used by the target Cassandra Database node. To know how to specify the remote port, refer to Enabling JMX Support for JRE.

JMX User and JMX Password

If JMX requires authentication only (but no security), then ensure that the user and password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to Configuring the eG Agent to Support JMX Authentication.

Confirm Password

Confirm the Password by retyping it in this text box.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Current data size

Indicates the current data size of the target node.



Data growth rate

Indicates the rate at which data is growing on the target node.




Indicates the rate at which unhandled exceptions occurred on the node during the last measurement period.


Ideally the value of this measure should be 0. A sudden/gradual increase of this measure indicates that too many unhandled exceptions have occurred. Administrators may need to troubleshoot the unhandled exceptions by checking the Errors and Fatal measures reported by the Cassandra Logs test.