Overview

Get metrics from Cassandra in real time to:

• Visualize and monitor Cassandra states.
• Be notified about Cassandra failovers and events.

Setup

Installation

The Cassandra check is included in the Datadog Agent package, so you don’t need to install anything else on your Cassandra nodes. It’s recommended to use Oracle’s JDK for this integration.

Note: This check has a limit of 350 metrics per instance. The number of returned metrics is indicated in the status page. You can specify the metrics you are interested in by editing the configuration below. To learn how to customize the metrics to collect see the JMX documentation for detailed instructions. If you need to monitor more metrics, contact Datadog support.

Configuration

Metric collection

1. The default configuration of your cassandra.d/conf.yaml file activate the collection of your Cassandra metrics. See the sample cassandra.d/conf.yaml for all available configuration options.

2. Restart the Agent.

Log collection

Available for Agent versions >6.0

For containerized environments, follow the instructions on the Kubernetes Log Collection or Docker Log Collection pages.

1. Collecting logs is disabled by default in the Datadog Agent, enable it in your datadog.yaml file:

   logs_enabled: true
   

2. Add this configuration block to your cassandra.d/conf.yaml file to start collecting your Cassandra logs:

     logs:
       - type: file
         path: /var/log/cassandra/*.log
         source: cassandra
         service: myapplication
         log_processing_rules:
            - type: multi_line
              name: log_start_with_date
              # pattern to match: DEBUG [ScheduledTasks:1] 2019-12-30
              pattern: '[A-Z]+ +\[[^\]]+\] +\d{4}-\d{2}-\d{2}'
   

   Change the path and service parameter values and configure them for your environment. See the sample cassandra.d/conf.yaml for all available configuration options.

   To make sure that stacktraces are properly aggregated as one single log, a multiline processing rule can be added.

3. Restart the Agent.

Validation

Run the Agent’s status subcommand and look for cassandra under the Checks section.

Data Collected

Metrics

Events

The Cassandra check does not include any events.

Service Checks

cassandra.can_connect
Returns CRITICAL if the Agent is unable to connect to and collect metrics from the monitored Cassandra instance, WARNING if no metrics are collected, and OK otherwise.
Statuses: ok, critical, warning

Troubleshooting

Need help? Contact Datadog support.

Further Reading

• How to monitor Cassandra performance metrics
• How to collect Cassandra metrics
• Monitoring Cassandra with Datadog

Cassandra Nodetool Integration

Overview

This check collects metrics for your Cassandra cluster that are not available through jmx integration. It uses the nodetool utility to collect them.

Setup

Installation

The Cassandra Nodetool check is included in the Datadog Agent package, so you don’t need to install anything else on your Cassandra nodes.

Configuration

Follow the instructions below to configure this check for an Agent running on a host. For containerized environments, see the Containerized section.

Host

1. Edit the file cassandra_nodetool.d/conf.yaml in the conf.d/ folder at the root of your Agent’s configuration directory. See the sample cassandra_nodetool.d/conf.yaml for all available configuration options:

   init_config:
   
   instances:
     ## @param keyspaces - list of string - required
     ## The list of keyspaces to monitor.
     ## An empty list results in no metrics being sent.
     #
     - keyspaces:
         - "<KEYSPACE_1>"
         - "<KEYSPACE_2>"
   

2. Restart the Agent.

Log collection

Cassandra Nodetool logs are collected by the Cassandra integration. See the log collection instructions for Cassandra.

Containerized

For containerized environments, use the official Prometheus exporter in the pod, and then use Autodiscovery in the Agent to find the pod and query the endpoint.

Validation

Run the Agent’s status subcommand and look for cassandra_nodetool under the Checks section.

Data Collected

Metrics

Events

The Cassandra_nodetool check does not include any events.

Service Checks

cassandra.nodetool.node_up
The agent sends this service check for each node of the monitored cluster. Returns CRITICAL if the node is down, otherwise OK.
Statuses: ok, critical

Troubleshooting

Need help? Contact Datadog support.

Further Reading

• How to monitor Cassandra performance metrics
• How to collect Cassandra metrics
• Monitoring Cassandra with Datadog