Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Capturing Cassandra metrics

Updated on March 11, 2021

This content applies only to On-premises and Client-managed cloud environments

Troubleshoot issues and monitor performance of the Cassandra cluster by gathering detailed metrics.

The following task provides an example for capturing max range slice latency. For a list of Cassandra metrics, see the Apache documentation.
  1. On the Decision Data Store node, download the JMXTerm executable JAR file by entering the following command: wget https://github.com/jiaqi/jmxterm/releases/download/v1.0.0/jmxterm-1.0.0-uber.jar
    For more information, see the JMXTerm documentation.
  2. From your console, run JMXTerm by entering the following command:java -jar jmxterm-1.0.0-uber.jar
  3. Open a connection to Cassandra JMX by entering the following command:open 127.0.0.1:7199
  4. Set the correct bean by entering the following command: bean org.apache.cassandra.metrics:type=ClientRequest,scope=RangeSlice,name=Latency
  5. Get statistic by entering the following command: get Max
  • Previous topic Nodetool commands for monitoring Cassandra clusters
  • Next topic Operating system metrics on Cassandra nodes

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us