The agent requires a connection to the cluster in order to gather information about the cluster and data structure. The agent may be referred to other nodes than the one specified.
- IP or Hostname – Host where Cassandra node is running. Default is “localhost”. (e.g.or )
- Port – The CQL native transport port for the Cassandra node. Default is 9042.
- Username – User that can connect to the Cassandra node.
- Password – Password of the user that can connect to the Cassandra node.
The agent requires JMX access to individual nodes in the cluster to gather most operational metrics.
- Port – The JMX listening port for the Cassandra node. This value will be used as the default value in the Node Connections list if no other value is provided. Default is 7199.
- Username – JMX User that can connect to the Cassandra node. This value will be used as the
- default value in the Node Connections list if no other value is provided.
- Password – Password of the JMX User that can connect to the Cassandra node. This value will be used as the default value in the Node Connections list if no other value is provided.
- Node Connections – IP or Hostnames for each node in the cluster must be added to this list in order for them to be monitored. Port, Username, and Password can be specified for each node. If no value is provided for these, the default values specified previously will be used. Check "Use as Host Alias?" to indicate that the value provided for "IP or Hostname" should be used as an alias for the discovered hostname for the respective node. Secondary Property Lists are global and can be shared between agents. To create a new property list for a different cluster, clone an existing list and then edit and save it as the selected list for that agent.
The Collection Interval fields in the agent properties are used to set the sample frequencies. You can turn off a collection by setting the interval to 0. The defaults are set based on the type of data being collected for relevancy. Currently, there is only one configurable collection period. Due to the format of the data being collected, it is important that data samples happen concurrently.
Aliases can optionally be added for Cassandra nodes in case hostnames as discovered by the agent differ from those used for the Hosts monitor. This Secondary Property List is a pairing of the uniquely identifying Host ID (a UUID string) and the desired hostname alias. There are two ways to determine a node’s Host ID for use in the Aliases list. For a node that has already been monitored for some time, the Host ID can be found on the Nodes Table of the Cassandra Clusters dashboard (the Host ID column is hidden by default, so it will need to be made visible via the table's "Show columns" dialog). Host IDs can also be queried directly from a specific Cassandra instance with the following CQL:
SELECT host_id FROM system.local WHERE key='local';
Two roles, Cassandra User and Cassandra Administrator, are installed with the cartridge. Viewing Cassandra dashboards requires that a user be assigned one of these or have the core Administrator role. Currently, there are no added privileges for the Cassandra Administrator role, but future cartridge versions which allow user interaction with the Cassandra cluster will require this role.