Redis is a fast, versatile data store that supports a variety of data structures, including strings, hashes, lists, sets, streams, and more. It also offers programmability, extensibility, persistence, clustering, and high availability. The community edition of Redis adds additional data models and capabilities, which include vector search, probabilistic data structures, JSON support, and full-text search.
The Redis Cloud integration is intended for use with Redis Cloud deployments of Redis software. It is not for use with Redis Enterprise installations. For Redis Enterprise, see the Datadog Redis Enterprise integration.
The integration provides metrics for three critical cluster components: databases, nodes, and shards, by using the Datadog Agent. This allows you to monitor database throughput, memory utilization, CPU usage, connection counts, replication health, and a variety of additional metrics within Datadog. You can use this information to understand the overall health of your Redis Cloud clusters, diagnose application performance issues, and prevent downtime.
For a full list of supported metrics, see the Metrics section below.
- Run the following command to install the Agent integration:
- For the Datadog Agent v6:
datadog-agent integration install -t datadog-redis_cloud==1.1.0
- For the Datadog Agent v7:
agent integration install -t datadog-redis_cloud==1.1.0
- Configure the integration by setting
openmetrics_endpointto your cluster's master node. See Getting Started with Integrations for more information. - Restart the Agent.
Set the openmetrics_endpoint to point to your cluster. See the example. Leave tls_verify set to false.
There are two optional parameters: extra_metrics and excluded_metrics, as noted in the example configuration file.
The extra_metrics parameter takes a list of metric groups. The following groups are available: RDSC.REPLICATION,
RDSC.NODE, RDSC.BIGSTORE, RDSC.FLASH, and RDSC.SHARDREPL. The default metrics groups RDSC.DATABASE,
RDSC.PROXY, RDSC.LISTENER and RDSC.SHARD are automatically inserted by the integration.
The exclude_metrics parameter takes a list of individual metrics to exclude, meaning that this information is not
passed on to Datadog. The individual metrics should be stripped of their prefix, meaning that 'rdsc.bdb_up'
becomes 'bdb_up'. The full list of metrics is available on the 'Data Collected' tab of the integration page, and in the Metrics section.
The following extra groups use the associated prefixes, which can be used to search for individual metrics on
the Data Collected page.
| Group | Prefix | Notes |
|---|---|---|
| RDSC.NODE | rdsc.node_ | This will return bigstore and flash metrics as well. |
| RDSC.DATABASE | rdsc.bdb_ | This will return replication metrics as well. |
| RDSC.SHARD | rdsc.redis_ | This will return shard replication metrics as well. |
| RDSC.REPLICATION | rdsc.bdb_crdt_ | |
| RDSC.REPLICATION | rdsc.bdb_replicaof_ | |
| RDSC.SHARDREPL | rdsc.redis_crdt_ | |
| RDSC.PROXY | rdsc.dmcproxy_ | |
| RDSC.LISTENER | rdsc.listener_ | |
| RDSC.BIGSTORE | rdsc.node_bigstore_ | |
| RDSC.FLASH | rdsc.node_available_flash | All flash metrics are of the form: rdsc.node_*_flash. |
-
Ensure you can ping the machine, particularly in a cloud environment. Run
wget --no-check-certificate <endpoint>orcurl -k <endpoint>to ensure that you can receive metrics. -
Check the status of the Datadog Agent.
The Redis Cloud integration gathers all metrics for databases, nodes, and shards.
See metadata.csv for a list of metrics provided by this integration.
The Redis Cloud integration does not include any service checks.
The Redis Cloud integration does not include any events.
Need help? Contact Redis Field Engineering.