Skip to main content

​
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.
DetailValue
CategorySecurity / observability
AuthenticationAPI key (and application key when required)
RegionDatadog is region-specific (US, EU, and so on). Use the org and endpoints that match your account.
Documentation: API and application keys, Authentication, 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

Complete this tab before you connect the source in Compliance.
1

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.
2

Open Organization Settings

From the left nav or avatar menu, choose Organization Settings (sometimes under Access or Administration, depending on layout).
3

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).
4

Create a new API key

Select New Key. Enter a name such as Iru Compliance and create the key.
Datadog caps API keys per organization (commonly 50). Delete unused keys if you are near the limit.
5

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.
Continue on the Iru Compliance tab.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Validate the API key string. Confirm you are using keys from the same org and site your tenant expects.
Some endpoints require both API and application keys. Supply both if prompted.
Back off and retry; large accounts may need wider sync windows. Check Datadog’s rate-limit headers on failing calls.
Align endpoints with your Datadog site (US vs EU vs other).

​
Considerations

API keys do not auto-expire: rotate on your own…

API keys do not auto-expire. Rotate on your own schedule and update Iru when you rotate.

Rate limits vary by endpoint; initial backfills can…

Rate limits vary by endpoint; initial backfills can take time on busy organizations.

Evidence reflects APIs your keys can…

Evidence reflects APIs your keys can access. Least-privilege keys may intentionally return narrower data.

Sources Management

Browse and manage every Compliance source.

Getting Started With Compliance

Frameworks, actions, and Artifacts.

Iru Overview

How Endpoint, Compliance, and Identity fit together.

Artifacts Management

Upload, review, and organize evidence from sources and actions.