{
  "schema_version": 2,
  "id": "integrate/datadog-with-redis-cloud/native",
  "title": "Native Datadog integration",
  "url": "https://redis.io/docs/latest/integrate/datadog-with-redis-cloud/native/",
  "summary": "Push Redis Cloud metrics directly to Datadog with the native, API-based integration, configured from the Redis Cloud console.",
  "tags": [
    "docs",
    "integrate",
    "rc"
  ],
  "last_updated": "2026-09-14T12:37:53-07:00",
  "page_type": "content",
  "content_hash": "1c2747b1078eb94ca09bb9ccd1acc2e31a0d2d327ba9f75b02780a2cb480b15d",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "The native Datadog integration pushes Redis Cloud metrics directly to your Datadog account over an API. You don't need a Datadog Agent, VPC peering, or any network configuration. Redis Cloud sends account-level metrics for all subscriptions and databases in your account, and provides a prebuilt dashboard.\n\n\nThe native Datadog integration is available on Redis Cloud Pro only. On Essentials plans, use the [agent-based Datadog integration](https://redis.io/docs/latest/integrate/datadog-with-redis-cloud) instead."
    },
    {
      "id": "how-the-native-integration-works",
      "title": "How the native integration works",
      "role": "content",
      "text": "- Redis Cloud pushes metrics to Datadog over an API, so there's no agent, VPC peering, or firewall configuration to manage.\n- You configure and manage the integration entirely from the Redis Cloud console. Setup takes about two minutes.\n- Metrics are account-level: they cover every subscription and database in your account, with automatic discovery of new subscriptions and databases.\n- Metrics appear in Datadog within about 30 seconds of activation.\n- A prebuilt dashboard is available in Datadog when you activate the integration.\n- The API key you provide is encrypted at rest and used only to push metrics. Redis Cloud never reads from or modifies your Datadog account."
    },
    {
      "id": "native-compared-to-agent-based",
      "title": "Native compared to agent-based",
      "role": "content",
      "text": "| | Agent-based | Native |\n|---|---|---|\n| Setup | Manual, per cluster | From the console, account-level |\n| Maintenance | Ongoing (reconfigure after redeployments) | None |\n| Data scope | Cluster-level/Subscription-level only | Account-level, with auto-discovery of subscriptions and databases |\n| Infrastructure | A Datadog Agent per cluster | None |\n\nThe [agent-based integration](https://redis.io/docs/latest/integrate/datadog-with-redis-cloud) remains available for Essentials plans and for Pro accounts that haven't migrated yet."
    },
    {
      "id": "prerequisites",
      "title": "Prerequisites",
      "role": "content",
      "text": "- An active Redis Cloud Pro subscription.\n- An active Datadog account.\n- Permission to create and manage Datadog API keys."
    },
    {
      "id": "create-a-datadog-api-key",
      "title": "Create a Datadog API key",
      "role": "content",
      "text": "In Datadog, go to **Organization Settings > API Keys > New Key**. Copy the key — you need it during setup."
    },
    {
      "id": "set-up-the-integration",
      "title": "Set up the integration",
      "role": "content",
      "text": "1. Sign in to the [Redis Cloud console](https://cloud.redis.io).\n1. Select **Account**, then open the **Integrations** tab.\n1. On the **Datadog** card (its status is **Not connected**), select **Configure**.\n1. Enter your Datadog API key and select your Datadog region, such as **US-1** or **EU-1**.\n1. Select **Connect**.\n\nThe Datadog integration appears on the **Account > Integrations** page:\n\n![images/rc/datadog-native-integrations-page.png](https://redis.io/docs/latest/images/rc/datadog-native-integrations-page.png)\n\nIn the **Datadog integration** dialog, enter your API key, select your API region, and select **Connect**:\n\n![images/rc/datadog-native-configure.png](https://redis.io/docs/latest/images/rc/datadog-native-configure.png)\n\nRedis Cloud validates the key and activates the integration. When validation succeeds, the Datadog card shows a green **Connected** badge.\n\n\nMake sure the region you select matches your Datadog account:\n\n- `app.datadoghq.com` → **US-1**\n- `app.datadoghq.eu` → **EU-1**"
    },
    {
      "id": "verify-the-connection",
      "title": "Verify the connection",
      "role": "content",
      "text": "The Datadog card shows a real-time status indicator:\n\n- **Connected** — metrics are being pushed successfully.\n- **Not connected** — the integration hasn't been activated.\n- **Connection error** — a push failure was detected.\n\nTo verify the end-to-end flow, select **Test connection**. Redis Cloud sends a test metric and updates the status automatically.\n\n![images/rc/datadog-native-connected.png](https://redis.io/docs/latest/images/rc/datadog-native-connected.png)"
    },
    {
      "id": "verify-metrics-in-datadog",
      "title": "Verify metrics in Datadog",
      "role": "content",
      "text": "Metrics begin appearing in Datadog within about 30 seconds. All Redis Cloud metrics use the `rdse2.` prefix.\n\nTo confirm that metrics are arriving:\n\n1. In Datadog, go to **Metrics > Explorer**.\n1. Search for `rdse2.db_config`.\n\nIf the metric returns data, metrics are reaching Datadog. If it doesn't, see [Troubleshoot](#troubleshoot).\n\nTo scope the metrics you view, use the **Subscription** and **Database** filters in the Redis Cloud dashboard."
    },
    {
      "id": "built-in-dashboard",
      "title": "Built-in dashboard",
      "role": "content",
      "text": "A prebuilt Redis Cloud dashboard is available in Datadog after you activate the integration. It covers key database metrics, including performance, memory utilization, latency, operations, connections, and cache efficiency. A link to the dashboard is available from the integration settings.\n\n![images/rc/datadog-native-dashboard.png](https://redis.io/docs/latest/images/rc/datadog-native-dashboard.png)\n\n\nIf the dashboard isn't available yet, import it manually: in Datadog, go to **Dashboards > New Dashboard > Import dashboard JSON**, then select the dashboard JSON file."
    },
    {
      "id": "metrics-reference",
      "title": "Metrics reference",
      "role": "content",
      "text": "All metrics use the `rdse2.` prefix. The following table lists a subset of the available metrics.\n\n| Metric | Description |\n|---|---|\n| `rdse2.db_config` | Database availability (1 = up, 0 = down) |\n| `rdse2.redis_server_used_memory` | Database memory usage |\n| `rdse2.db_memory_limit_bytes` | Configured memory limit |\n| `rdse2.redis_server_db_keys` | Number of keys in the database |\n| `rdse2.endpoint_read_requests` | Total read commands received by the proxy endpoint |\n| `rdse2.endpoint_write_requests` | Total write commands received by the proxy endpoint |\n| `rdse2.endpoint_other_requests` | Total non-read/write commands received by the proxy endpoint |\n| `rdse2.endpoint_read_requests_latency_histogram_sum` | Cumulative sum of read request latency observations (µs) |\n| `rdse2.endpoint_read_requests_latency_histogram_count` | Cumulative count of read request latency observations |\n| `rdse2.endpoint_write_requests_latency_histogram_sum` | Cumulative sum of write request latency observations (µs) |\n| `rdse2.endpoint_write_requests_latency_histogram_count` | Cumulative count of write request latency observations |\n| `rdse2.endpoint_other_requests_latency_histogram_sum` | Cumulative sum of other request latency observations (µs) |\n| `rdse2.endpoint_other_requests_latency_histogram_count` | Cumulative count of other request latency observations |\n| `rdse2.redis_server_connected_clients` | Number of client connections currently open to this shard |\n| `rdse2.redis_server_keyspace_read_hits` | Cumulative successful read-command key lookups (cache hits) |\n| `rdse2.redis_server_keyspace_read_misses` | Cumulative read-command key lookups that missed |\n| `rdse2.redis_server_keyspace_write_hits` | Cumulative successful write-command key lookups |\n| `rdse2.redis_server_keyspace_write_misses` | Cumulative write-command key lookups that missed |\n| `rdse2.node_memory_MemFree_bytes` | Free memory on the host node, in bytes |"
    },
    {
      "id": "migrate-from-the-agent-based-integration",
      "title": "Migrate from the agent-based integration",
      "role": "content",
      "text": "Both the agent-based and native integrations can run in parallel. You can enable the native push integration without downtime, then disable the legacy agent afterward.\n\nTo avoid a gap in observability, complete the migration and verify that metrics are arriving in Datadog before you disable the Datadog Agent. Data collected by the legacy agent remains available in its existing dashboard."
    },
    {
      "id": "manage-the-integration",
      "title": "Manage the integration",
      "role": "content",
      "text": "1. Sign in to the [Redis Cloud console](https://cloud.redis.io).\n1. Select **Account**, open the **Integrations** tab, and select **Manage** on the Datadog card.\n\nFrom there, you can:\n\n- Test the connection.\n- Disable the integration.\n\nTo replace the API key or change the Datadog region, disable the integration, then set it up again with the new key or region."
    },
    {
      "id": "troubleshoot",
      "title": "Troubleshoot",
      "role": "errors",
      "text": ""
    },
    {
      "id": "the-connection-test-fails",
      "title": "The connection test fails",
      "role": "content",
      "text": "- Verify that the Datadog API key is correct.\n- Make sure the Datadog region you selected matches your account.\n- Confirm that the API key is active and has the required permissions."
    },
    {
      "id": "no-metrics-appear-after-a-few-minutes",
      "title": "No metrics appear after a few minutes",
      "role": "content",
      "text": "- Confirm that the integration status is **Connected** in the Redis Cloud console.\n- In Datadog, go to **Metrics > Explorer** and search for `rdse2.db_config`. If the metric exists, data is reaching Datadog. If not, recheck the integration configuration and API key."
    }
  ],
  "examples": []
}