How Does eG Enterprise Monitor Cassandra Database?

eG Enterprise can monitor the Cassandra Database in an agent-based or an agentless manner. In case of the agentless approach, the remote agent used to monitor the Cassandra Database should be deployed on a remote Windows host in the environment.

Pre-Requisites for Monitoring the Cassandra Database

• Regardless of the approach (agent-based or agentless), the eG agent should be configured to connect to the JRE used by the Cassandra Database so that the eG agent can pull out the required metrics, using JMX methodology.

• By default, JMX requires no authentication or security (SSL). In this case therefore, to use JMX for pulling out metrics from the Cassandra Database, the following needs to be done:

  • Login to the Cassandra Database host.

  • The <CASSANDRA_HOME>\conf folder used by the target application will typically contain the following files:

    • cassandra-env.ps1 or cassandra-env.sh

    • jmxremote.password
    • jmxremote.access
  • Edit the cassandra-env.ps1 or cassandra-env.sh file and set the port number at which the JMX listens to. If the JMX listens to port 7199, then set the port number as 7199.
  • Then save the file.

  • Next, during test configuration, do the following:

    • Set JMX as the mode;
    • Set the port that you defined in step 3 above (in the cassandra-env.ps1 or cassandra-env.sh file) as the jmx remote port;
    • Set the user and password parameters to none.
    • Update the test configuration.

To know how to enable JMX support for JRE, refer to the Configuring the eG Agent to Support JMX Authentication topic.