This page provides configuration details for Cassandra collectors.
To monitor Cassandra with Database Visibility, you must be running version:
- Apache Cassandra >= 3.11.4
- Datastax Enterprise (DSE) Cassandra >= 6.7.3
|Create New Collector
|The Database type that you want to monitor.
|The Database Agent that manages the collector.
|The name you want to identify the collector by.
|Hostname or IP Address
|The hostname or IP address of the machine that your database is running on.
|The TCP/IP address of the port on which your database communicates with the Database Agent.
|The port to remotely connect through JMX (optional for DSE Cassandra). See JMX Configurations.
|The name of the JMX user who is connecting to and monitoring the database using the Database Agent. See JMX configurations.
|The password of the JMX user who is connecting to and monitoring the database through the Database Agent.
|Username and Password
The name of the user who is connecting to and monitoring the database using the Database Agent. The user must have the permissions described in:
|The password of the user who is connecting to and monitoring the database through the Database Agent.
Click to enable SSL Connection:
If you also use client certificate authentication, then click the Enable SSL Client Authentication box.
You can set the context protocol for the SSL environment using the
These platforms support TLSv1.3:
If a JDK version does not support TLSv1.3 or the specified context protocol, AppDynamics switches to TLSv1.2.
|Monitor Operating Systems
|See Configure the Database Agent to Monitor Server Hardware.
These are the required configurations:
Query Capture Configurations
JMX Configurations for Apache/DSE Cassandra
- To enable JMX for:
local connection, under the if [ "$LOCAL_JMX" = "yes" ]; then statement, set:
for remote connection, under the corresponding else statement, set:
Set the path to the credentials file,
JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.password.file=PATH TO FILE"CODE
jmxremote.passwordfile, set JMX credentials to be the same as that of the database user credentials to be specified in the collector configuration:
You may choose to give ReadOnly JMX access to the database monitoring user by defining in the
jmxremote.accessfile as mentioned in Enabling JMX authentication and authorization.
If DB and JMX have different SSL key stores, use:
- The DB SSL properties in the Controller collector configuration
- The system properties to set the JMX SSL properties
-Djavax.net.ssl.keyStore="<path-to-clientKeyStore>" -Djavax.net.ssl.keyStorePassword=<keystore-password> -Djavax.net.ssl.trustStore="<path-to-clientTruststore>" -Djavax.net.ssl.trustStorePassword=<client-truststore-password>CODE
If JMX SSL is disabled, set "-Dcassandra.jmx.ssl.enabled" = false and if JMX SSL is enabled, then set "-Dcassandra.jmx.ssl.enabled" = true.
To monitor the JMX SSL-enabled Cassandra database, add the following properties:
Dcassandra.jmx.ssl.enabled=true -Djavax.net.ssl.trustStore="<truststore location>" -Djavax.net.ssl.trustStorePassword=<password>CODE
If you are using a single Database Agent to monitor multiple Cassandra clusters where each Cassandra cluster has different root CAs.
Then, to monitor these Cassandra clusters with different keystore credentials, create one trust store that contains all root CAs of Cassandra clusters and Controller certificates.
For example, to import two root CAs, run the following command:
keytool -import -alias <alias-of-CA1> -file <root-CA-of-DB1> -keystore <truststore-location1> -storepass <truststore-password1> keytool -import -alias <alias-of-CA2> -file <root-CA-of-DB2> -keystore <truststore-location1> -storepass <truststore-password1>CODE
For more information, see Enable SSL and SSH for Database Agent Communications.
If you cannot create a single trust store, use different Database Agents while monitoring different Cassandra clusters.