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.

Performing regular monitoring activities on a Cassandra cluster

Updated on April 5, 2022

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

Verify that the Cassandra cluster is in good health by performing the recommended monitoring activities on a regular basis.

  • Monitor Pega alerts for the Decision Data Store (DDS) to discover the causes of performance issues and learn how to resolve them.
    For more information, see Pega alerts for Cassandra.
  • Review the monitoring information on the DDS service landing page. For information about accessing the DDS service landing page, see Monitoring decision management services.
    On the DDS service landing page, you can capture basic and comparative data. Apart from monitoring the cluster metrics, verify that all members of the cluster provide similar performance.
  • Run nodetool monitoring commands, for example, to access an overview of the cluster health, or to retrieve a list of active and pending tasks.
  • Analyze operating system metrics, such as IO bottlenecks or network buffer buildups, to detect problems with 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