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

# Datadog

> Connect Datadog to Iru Compliance with API and application key credentials to collect monitor configuration, user inventory, and security-posture evidence.

### About Datadog

The **Datadog** connector reads account configuration and security-oriented data: monitors, users and teams, integrations posture, and related settings. You can attach this evidence to controls in Iru Compliance. Transport uses Datadog’s HTTP APIs with your **API key** (`DD-API-KEY`). Some read paths may also require an **application key** (`DD-APPLICATION-KEY`); the in-product wizard reflects what Iru needs for your tenant.

### How It Works

Datadog separates keys by purpose:

* **API keys** authenticate data plane traffic and many configuration reads via `DD-API-KEY`.
* **Application keys** pair with API keys for certain configuration APIs via `DD-APPLICATION-KEY`.

The connector focuses on **read** operations for compliance evidence. **Iru does not ship custom metrics or logs** into Datadog as part of this source.

| Detail             | Value                                                                                                  |
| ------------------ | ------------------------------------------------------------------------------------------------------ |
| **Category**       | Security / observability                                                                               |
| **Authentication** | API key (and application key when required)                                                            |
| **Region**         | Datadog is **region-specific** (US, EU, and so on). Use the org and endpoints that match your account. |

Documentation: [API and application keys](https://docs.datadoghq.com/account_management/api-app-keys/), [Authentication](https://docs.datadoghq.com/api/latest/authentication/), [Rate limits](https://docs.datadoghq.com/api/latest/rate-limits/).

### Prerequisites

* **Org Admin** (or equivalent) access to create keys in Datadog.
* Awareness of your **Datadog site** (`datadoghq.com`, `datadoghq.eu`, FedRAMP variants, and so on).

### Connect Datadog to Iru

<Tabs>
  <Tab title="Datadog">
    <Note>
      Complete this tab before you connect the source in Compliance.
    </Note>

    <Steps>
      <Step title="Sign in to the correct Datadog site">
        Open your org’s Datadog URL (for example **`app.datadoghq.com`**, **`app.datadoghq.eu`**, or your **FedRAMP** / **Gov** host). Sign in with a role that can manage **Organization Settings**.
      </Step>

      <Step title="Open Organization Settings">
        From the left nav or avatar menu, choose **Organization Settings** (sometimes under **Access** or **Administration**, depending on layout).
      </Step>

      <Step title="Open API Keys">
        Select **API Keys**. You should see existing keys and a control to create a new one (path similar to **Organization Settings** → **API Keys**).
      </Step>

      <Step title="Create a new API key">
        Select **New Key**. Enter a name such as **Iru Compliance** and create the key.

        <Note>
          Datadog caps **API keys per organization** (commonly **50**). Delete unused keys if you are near the limit.
        </Note>
      </Step>

      <Step title="Copy the API key to a secure store">
        **Copy** the key value immediately and store it like a password until you paste it in **Iru Compliance**. Datadog may show the full value only at creation.
      </Step>
    </Steps>

    <Note>
      Continue on the [**Iru Compliance**](#iru-compliance) tab.
    </Note>
  </Tab>

  <Tab title="Iru Compliance">
    <Note>
      Finish the [**Datadog**](#datadog) tab first.
    </Note>

    <Steps>
      <Step title="Open Sources">
        In Iru Compliance, on the left navigation bar, expand **Compliance** and select **Sources**.

        <Frame>
          <img src="https://mintcdn.com/iru/7HsGH7lnQ8GpVmI0/assets/media/images/iru-navigation-compliance-sources.png?fit=max&auto=format&n=7HsGH7lnQ8GpVmI0&q=85&s=595982441fd777b333b3ecfea24adc24" alt="Left navigation: Compliance expanded, Sources selected" width="424" height="1056" data-path="assets/media/images/iru-navigation-compliance-sources.png" />
        </Frame>
      </Step>

      <Step title="Turn on Datadog">
        Find **Datadog** (set **Category** to **Monitoring** or use **Search by name or description**). On that card, turn on the **toggle**. A browser tab or window may open for the connector wizard.
      </Step>

      <Step title="Enter the Datadog API key">
        When the wizard asks for it, paste your Datadog **API key**.
      </Step>

      <Step title="Add an application key if prompted">
        If the wizard asks for an **application key**, create one in Datadog under **Organization Settings** → **Application Keys**, then paste it (and the API key if asked again) in the wizard.
      </Step>

      <Step title="Finish the connection">
        Click **Submit API Key**. When the connection succeeds, the wizard shows **Connection Configured**.
      </Step>

      <Step title="Confirm the source is Active">
        Close the **Iru is requesting access to external services** browser tab, then return to **Compliance** → **Sources** and confirm the **Datadog** card is **Active**.
      </Step>
    </Steps>
  </Tab>
</Tabs>

### Troubleshooting

<AccordionGroup>
  <Accordion title="Nothing opens when you turn the source on">
    Check **pop-up blocker** settings for the Iru site and try again.
  </Accordion>

  <Accordion title="403 Forbidden / unauthorized">
    Validate the API key string. Confirm you are using keys from the **same org and site** your tenant expects.
  </Accordion>

  <Accordion title="Incomplete data">
    Some endpoints require **both** API and application keys. Supply both if prompted.
  </Accordion>

  <Accordion title="429 rate limits">
    Back off and retry; large accounts may need wider sync windows. Check Datadog’s rate-limit headers on failing calls.
  </Accordion>

  <Accordion title="Wrong region">
    Align endpoints with your Datadog site (US vs EU vs other).
  </Accordion>
</AccordionGroup>

### Considerations

<CardGroup cols={2}>
  <Card title="API keys do not auto-expire: rotate on your own…" icon="circle-info">
    API keys **do not auto-expire**. Rotate on your own schedule and update Iru when you rotate.
  </Card>

  <Card title="Rate limits vary by endpoint; initial backfills can…" icon="shield">
    Rate limits vary by endpoint; initial backfills can take time on busy organizations.
  </Card>

  <Card title="Evidence reflects APIs your keys can…" icon="server">
    Evidence reflects APIs your keys can access. Least-privilege keys may intentionally return narrower data.
  </Card>
</CardGroup>

### Related Articles

<CardGroup cols={2}>
  <Card title="Sources Management" icon="plug" href="/en/compliance/sources-management">
    Browse and manage every Compliance source.
  </Card>

  <Card title="Getting Started With Compliance" icon="rocket" href="/en/compliance/getting-started-with-compliance">
    Frameworks, actions, and **Artifacts**.
  </Card>

  <Card title="Iru Overview" icon="layer-group" href="/en/iru/platform-overview/iru-overview">
    How Endpoint, Compliance, and Identity fit together.
  </Card>

  <Card title="Artifacts Management" icon="folder-open" href="/en/compliance/artifacts-management">
    Upload, review, and organize evidence from sources and actions.
  </Card>
</CardGroup>