Monitoring Redis Cloud with Prometheus and Datadog – Redis Knowledge Base

Redis Cloud Pro enables advanced observability through an internal Prometheus-compatible metrics endpoint. These metrics can be scraped using Prometheus and visualized through Grafana or exported to Datadog for real-time monitoring and alerting. This guide walks through Prometheus and Datadog integration prerequisites, step-by-step setup, common troubleshooting scenarios, and helpful links. Monitoring is not supported on Essentials due to the lack of VPC peering or Private Service Connect (PSC) capabilities.

Prerequisites

Cloud Pro subscription with private networking enabled

VPC Peering or Private Service Connect from your monitoring VPC to Redis Cloud is required.
Essentials tier does not support Prometheus or Datadog integration.
Redis Cloud API credentials (username/password) for Datadog authentication.

Prometheus, Datadog, and optionally Grafana

Prometheus (via Docker or Helm) to scrape the internal metrics.
Datadog Agent with OpenMetrics enabled, running inside the peered VPC.
Grafana (optional) for direct visualization of Prometheus metrics.

Access to internal metrics endpoint

Prometheus and Datadog Agent must be able to reach https://<internal_host>:8070/v2.
Port 8070 must be open through VPC routes and security groups.

Step-by-Step Setup

1. Locate the Metrics Endpoint

In the Redis Cloud Console:
Navigate to Databases › Configuration, copy the Internal Host, and replace the port with 8070.

2. Configure Prometheus
Create a basic prometheus.yml configuration:

global:
  scrape_interval: 15s

scrape_configs:
  - job_name: 'redis-enterprise-cloud'
    scheme: https
    tls_config:
      insecure_skip_verify: true
    static_configs:
      - targets: ['<internal_host>:8070']

3. Deploy Prometheus (and optionally Grafana)
Use Docker Compose to deploy:

docker compose up -d

Then visit Prometheus UI → Status › Targets to verify the redis-enterprise-cloud target is UP.

4. Set Up Datadog Integration
In the Datadog UI:

Go to Integrations › Redis Cloud and install the integration.

Edit the Datadog config file:

# /etc/datadog-agent/conf.d/redis_cloud.d/conf.yaml
instances:
  - openmetrics_endpoint: https://<internal_host>:8070/v2
    namespace: rdsc
    ssl_verify: false

Restart the Datadog Agent and open Metrics › Explorer to confirm rdsc metrics are flowing.
5. Verify Data in Datadog:

Go to the Datadog console and navigate to Infrastructure > Host Map. Look for the host that monitors your Redis Cloud instance. Please ensure that it appears in the list and has a section called “rdsc” which stands for Redis Cloud’s namespace integration.
You can also check metrics, go to Metrics > Explorer and enter rdsc.bdb_up to see if the metrics are being captured.

Troubleshooting

Issue	Possible Cause	Suggested Fix
Prometheus target is DOWN	VPC routing or security groups may be blocking port 8070	Confirm networking and security group rules; check metrics exporter is enabled
No metrics in Datadog	Agent misconfiguration or invalid OpenMetrics setup	Verify `namespace: rdsc` is present and logs show successful scrape attempts
TLS handshake errors	Certificate validation failure (common in dev/test environments)	Set `ssl_verify: false` for testing; use valid CA bundle in production setups
Authentication failures	Missing or incorrect Redis Cloud credentials	Verify username/password in configuration

Common Pitfall: Essentials Plan Limitation
Customers using the Essentials plan cannot access the metrics endpoint due to lack of private networking. To use Prometheus or Datadog, upgrade to a Pro subscription.