Skip to main content

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.

​
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

​
Datadog

1

Open API Keys

Sign in to Datadog. Go to Organization Settings → API Keys (for example https://app.datadoghq.com/organization-settings/api-keys on the US commercial site).
2

Create and store an API key

Select New Key. Enter a name such as Iru Compliance, create the key, and copy it to a secure store. Keys are secrets; treat them like passwords.
Datadog caps API keys per organization (commonly 50). Delete unused keys if you are near the limit.

​
Iru Compliance

1

Open Sources

In Iru Compliance, on the left navigation bar, expand Compliance and select Sources.
Left navigation: Compliance expanded, Sources selected
2

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

Enter the Datadog API key

When the wizard asks for it, paste your Datadog API key.
4

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

Confirm the source is Active

Complete any remaining prompts until the Datadog card shows Active.

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

​
See also