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

# Datadog

> Connect Datadog to Layer to collect monitor uptime, downtime schedules, and log retention evidence for SOC 2 availability and confidentiality criteria.

The Datadog integration pulls monitors, downtime windows, and log index configurations from your Datadog account. This data feeds compliance evidence for availability and incident-response controls in [Axiom Codex](/codex/index).

## What you'll need

* A Datadog account with permission to create API and application keys.
* Two minutes.

## Set it up

<Steps>
  <Step title="Create an API key">
    In Datadog, go to **Organization Settings → API Keys** and click **New Key**. Name it `Axiom Layer` and copy the key value.
  </Step>

  <Step title="Create an application key">
    Go to **Organization Settings → Application Keys** and click **New Key**. Name it `Axiom Layer` and copy the key value.
  </Step>

  <Step title="Paste both keys into Layer">
    In Layer, go to **Integrations**, find Datadog, and click **Connect**. Paste the **API Key** and **Application Key**, then click **Connect**.

    <Note>
      If your Datadog account uses a regional site (for example `api.datadoghq.eu` or `api.us5.datadoghq.com`), enter the site hostname in the **Site** field. Leave it blank for the default US1 site.
    </Note>
  </Step>

  <Step title="Wait for the first sync">
    The initial sync runs immediately and typically finishes in under five minutes.
  </Step>
</Steps>

## What gets synced

| Object      | Fields                            | Refresh cadence |
| ----------- | --------------------------------- | --------------- |
| Monitors    | name, type, status, tags          | Daily           |
| Downtimes   | scope, start/end, active status   | Daily           |
| Log indexes | name, retention days, daily limit | Daily           |

## Compliance evidence

Datadog data generates evidence records for the following SOC 2 controls:

| Evidence                            | Controls     |
| ----------------------------------- | ------------ |
| Monitor uptime and SLA posture      | CC7.2, A1.2  |
| Downtime and alert policy inventory | CC7.2, CC7.3 |
| Log index retention settings        | CC7.2, CC6.1 |

See the [SOC 2 evidence catalog](/codex/soc2-evidence-catalog) for full control descriptions.

## Required permissions

The API key authenticates requests to Datadog's API. The application key determines the scope of data your requests can access — it inherits the permissions of the Datadog user who created it. A user with the **Datadog Read Only** role is sufficient.

## Troubleshooting

<AccordionGroup>
  <Accordion title="403 Forbidden on first sync">
    The application key may belong to a user without read permissions. Create the application key from a user account that has at least the **Datadog Read Only** role.
  </Accordion>

  <Accordion title="No monitors or log indexes appear">
    Verify that your Datadog account has monitors configured and that the API key belongs to the correct organization. If you have multiple Datadog organizations, make sure you're generating keys in the right one.
  </Accordion>

  <Accordion title="I use a non-US Datadog site">
    Enter your regional site hostname (for example `api.datadoghq.eu`) when connecting. If you connected without specifying a site, disconnect and reconnect with the correct hostname.
  </Accordion>
</AccordionGroup>