Cassandra is an open source distributed database management system. We use the Jolokia agent to monitor Cassandra’s performance as Cassandra exposes its metrics via JMX. Jolokia connects to a given mbean server and then exposes the server via a REST-like interface, acting as a bridge between JMX and HTTP/JSON.

Metricly supports all versions of Cassandra, but minor issues could be present in versions we haven’t tested specifically. In particular, the Metricly Agent version 5.1 has been tested against Cassandra versions 2.0.17 and 2.1.15. There’s a known issue with the 5.1 agent against Cassandra 3.0.10.


If you haven’t installed the Linux agent already, see the instructions on this page for how to install it. If you need to disable the Linux integration or view the unique API key assigned to your account, navigate to the Integrations page under the user account drop-down menu and click the integration designated as Infrastructure under the Integration column.

Collector Configuration

  1. Download the Jolokia JVM JAR file.
    1. Move the downloaded file to the /opt/netuitive-agent/ directory.
    2. Add the following line to the very end of the file (typically located in /etc/cassandra/conf or /opt/cassandra/conf):
      JVM_OPTS="$JVM_OPTS -javaagent:/opt/netuitive-agent/jolokia-jvm-1.3.4-agent.jar"

      When adding this line to your file, ensure that the quotes are not automatically formatted to be smart quotes. Smart quotes will prevent Cassandra from starting.
      If you’re running Cassandra in a container, you’ll need to add –javaagent:/opt/agent.jar=port=8778,host= to the end of the line above.
    3. Restart Cassandra, and confirm Jolokia is running by accessing http://localhost:8778/jolokia/
  2. After installing Jolokia, navigate to the collectors folder. The default location is /opt/netuitive-agent/conf/collectors.
  3. Open the CassandraJolokiaCollector.conf file.
  4. Change the enabled setting to True, save the file, and restart the Linux agent.
    This integration’s package (computed metrics, dashboards, and policies that will give you important events and alerts) will be automatically enabled and provisioned to your account as soon as Metricly receives data from the integration. The PACKAGES button on the integration setup page will become active once data is received, so you’ll be able to disable and re-enable the package at will.

Additional Configuration Options

Collector Options

Option Default Description
enabled False Enable collecting Cassandra metrics.
host localhost Hostname to collect from.
port 8778 Port to collect from.
path cassandra The metric prefix, e.g., how you want the metrics to show up in Metricly.
jolokia_path jolokia Part of the URL path that points to where your application serves metrics. Typically jmx or jolokia.
mbeans org.apache.cassandra.metrics Pipe ( | ) delimited list of MBeans for which to collect stats. If no list is provided, all MBeans stats will be collected.




Regex list to match metrics to block. Mutually exclusive with metrics_whitelistoption.
byte_unit Default numeric output(s).
histogram_regex Filter to only process attributes that match the specified regex.
measure_collector_time Measure the collector’s run time in milliseconds.
metrics_whitelist Regex list to match metrics to transmit. Mutually exclusive with metrics_blacklistoption.
password Password used for authentication.
percentiles Comma separated list of statistical percentiles to collect.
regex Enables the mbeans option to match with regex.
rewrite Config sub-section that contains pairs of from-to regex rewrites.

The rewrite subsection should exist directly underneath the mbeans option like so:

mbeans = "..."
java = coffee
"-v\d+\.\d+\.\d+" = "-AllVersions"
".*Gets2Activities.*" = ""...
username Username used for authentication.



Redhat 6 and 7
CentOS 6 and 7
Amazon Linux (latest)
Ubuntu 12, 14, 15, and 16
Debian 7, 8, and 9


Linux Agent



Due to the sheer volume of Cassandra metrics, the individual metrics won’t be documented here. Instead, here are some general properties of the groups of metrics:

  • All metrics share the following properties:
    • Type: GAUGE
    • Statistic: average
    • Min: 0
    • Sparse Data Strategy: None
    • BASE
    • CORR
    • UTIL
  • For metrics that end with Latency.OneMinuteRate:
    • Unit = ms (milliseconds)
  • For OneMinuteRate metrics that are not Latency:
    • Unit = ops (operations per second)
  • For metrics that contain HeapSizeDataSizeDiskSpaceMemory, or RowSize:
    • Unit = bytes
  • For metrics ending with HitRate or Ratio:
    • Unit = percentunit (i.e. percentage represented as a value between 0 and 1)
    • Max = 1