Apache Cassandra CQL Backends
By default, Splunk AppDynamics automatically detects and identifies exit calls to Apache Cassandra using Thrift and DataStax drivers.
Note: Exceptions returned from Cassandra backends show up as separate exit calls. For the DataStax 1.0 driver, the Java Agent detects an "unknown" Cassandra backend in order to capture the error details.
Cassandra Backend Naming Properties
You can enable or disable the use of the properties below for Cassandra backend identification:
Note: When you configure Cassandra backend naming, consider the following:For DataStax clients, Splunk AppDynamics does not recommend using the keyspace property. Due to driver limitations, the keyspace property is only available when Statement.setKeyspace is called explicitly in Cassandra. This can lead to the discovery of multiple backends.Thrift clients don't support Cluster Name, Rack or Data Center properties, so those properties return null for Thrift.
| Configurable Properties | Default Automatic Cassandra CQL Backend Discovery/Naming |
|---|---|
| Cluster Name | Yes |
| Keyspace | No |
|
Host |
Yes |
|
Port |
Yes |
|
Data Center |
No |
|
Rack |
No |