Datadog integration¶

Connect DXDT to Datadog for read-only observability — monitors, hosts, metrics, events, and incidents. DXDT reads your telemetry to correlate signals during investigations.


Setup time	~6 minutes
Difficulty	Easy

Access required: Datadog admin (to create an Application Key), or a teammate who is

Prerequisites¶

A Datadog account and knowledge of your site (e.g. datadoghq.com, datadoghq.eu, us5.datadoghq.com).
Permission to create an API key and an Application key.

Setup¶

1. Find your Datadog site¶

Look at the URL you use for Datadog. The domain after app. is your site — e.g. app.datadoghq.eu → site datadoghq.eu. US1 users see app.datadoghq.com → site datadoghq.com.

Note

Using the wrong site is the most common setup mistake — API and App keys are region-specific.

2. Create an API key¶

Go to Organization Settings → API Keys and click New Key. Name it DXDT and copy the value.

3. Create an Application key¶

Go to Organization Settings → Application Keys and click New Key. Name it DXDT and copy the value.

Note

Application keys inherit the permissions of the creator. For least privilege, create the key under a service account whose role has only read/monitor-read scopes.

4. Keep both keys handy¶

You'll paste the API key and the Application key into DXDT along with your site.

Configuration fields¶

Field	Where to find it
API Key (`api_key`)	The API key from Step 2.
Application Key (`app_key`)	The Application key from Step 3.
Site (`site`)	Your Datadog site from Step 1, e.g. `datadoghq.com`, `datadoghq.eu`, `us5.datadoghq.com`. Defaults to `datadoghq.com` if left blank.

Verify the connection¶

Open the Configuration tab, enter both keys and your site, and click Install & Configure. The Live Status panel should confirm the keys are valid and show the resolved API base URL.

Security

Keys are stored encrypted per-tenant. DXDT uses them for read-only queries; create the Application key under a least-privilege service account where possible.

Troubleshooting¶

403 Forbidden on API key validation

The site is wrong, or the keys belong to a different Datadog region/org. Double-check your site value and that both keys were created in that same Datadog organization.

API key valid but data requests fail

The Application key is missing or under-privileged. Confirm the Application key is set, and that its owner's role can read monitors, hosts, and events.

Wrong region entirely

EU/US mismatch. EU tenants must use datadoghq.eu; the default datadoghq.com is US1 only.

Vendor documentation: https://docs.datadoghq.com/account_management/api-app-keys/