> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Datadog

> Connect Datadog to nOps for unified observability cost visibility

## Overview

nOps uses your **Datadog API key**, **App key**, and **site** to pull cost and usage data into Inform. Credentials are stored securely, validated before save, and are not shown again in the nOps UI after you connect.

## Prerequisites

* A Datadog account with permission to create or use API and application keys
* Datadog **App key** with `usage_read` and `billing_read` scopes enabled
* nOps organization **administrator** access to connect or manage the integration

<Note>
  **Members** can view integration status on **Settings** and **Integrations**, but only **admins** and **owners** can connect, re-validate, or disconnect. Non-admins see an **Admin Only** indicator on connectable cards.
</Note>

## Authentication requirements

nOps requires both a **Datadog API key** and **Datadog App key**. The App key must have **`usage_read`** and **`billing_read`** permissions so nOps can retrieve cost and usage data.

## Create Datadog API key

1. Sign in to your [Datadog account](https://app.datadoghq.com).
2. Press **Ctrl+K** (Windows/Linux) or **⌘+K** (Mac) to open the Datadog search bar.
3. Type `/organization-settings/api-keys` and press **Enter**.
4. Click **New Key**, name the key (for example `API key for nOps`), and click **Create API key**.
5. Copy the **API key** value (not the Key ID) and store it securely.

## Create Datadog App key

1. Press **Ctrl+K** (Windows/Linux) or **⌘+K** (Mac) to open the Datadog search bar.
2. Type `/organization-settings/application-keys` and press **Enter**.
3. Click **New Key**, name the key (for example `Application key for nOps`), and click **Create Application key**.
4. Copy the **Application key** value and store it securely.
5. Click **Edit** on the new App key, enable **`usage_read`** and **`billing_read`**, and click **Save**.

<Warning>
  Without `usage_read` and `billing_read` on the App key, nOps cannot sync Datadog cost and usage data, even if the key itself is valid.
</Warning>

### If you cannot enable billing scopes

Ask your **Datadog organization administrator** to edit the App key under **Organization Settings → Application Keys**, enable **`usage_read`** and **`billing_read`**, and save. Then try **Connect** again in nOps.

## Connect in nOps

Only nOps administrators can complete these steps.

### Where to open Datadog

* **To connect for the first time** — go to **Settings → Integrations** (open the full catalog via `/settings/integrations` or **View all** from the Settings preview) and click the **Datadog** card.
* **To manage an existing connection** — go to **Settings → Account Status → Connected apps** and click the **Datadog** chip to re-validate or disconnect.

### Connect steps

1. Click the **Datadog** card or chip.
2. Enter your **Datadog API key**, **Datadog App key**, and select your **Datadog site** (for example `datadoghq.com` or `datadoghq.eu`). See [Datadog sites](https://docs.datadoghq.com/getting_started/site/#access-the-datadog-site).
3. Click **Connect**.

nOps validates both keys with Datadog before storing them. If validation succeeds, the catalog shows **Integrated** or Connected apps shows **Connected**.

## Manage your connection

After Datadog is connected, administrators can open the same card or chip to:

* **Re-validate** — nOps checks the stored keys against Datadog again without re-entering them.
* **Disconnect** — removes the stored keys and marks the integration as disconnected.

If validation fails, the status changes to **Action required**. Update or rotate keys in Datadog, then **Re-validate** or connect again with new keys.

## Troubleshooting

### Invalid credentials

* Confirm the API key and App key were copied in full with no extra spaces.
* Ensure the **Datadog site** matches the site you use to sign in to Datadog.
* If the keys validate but no cost data appears, verify the App key has **`usage_read`** and **`billing_read`** enabled.

### Data not appearing

* Allow up to **24 hours** for the initial Inform sync after a successful connect.
* Confirm there is billable Datadog usage in the account.

### Admin Only on the card

* You are signed in as a **member**. Ask an org admin to connect or manage Datadog.

## Security

Treat API and App keys like passwords. Do not share them in chat, email, or source control. Rotate keys in Datadog if they may have been exposed.