Integrations / Datadog

Datadog

Datadog monitoring and analytics platform

Multiple fields

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A Datadog organization.

Permission to create an application key (usually admin or standard with that privilege).

Vendor setup

Get the credential

Open Organization Settings

In Datadog, open Organization Settings → Application Keys (and API Keys).

Create the keys Datadog asks Telara to store

Create the key pair the Connect dialog lists. Do not paste a browser session cookie.

Paste in Telara

Settings → Integrations → Datadog.

In Telara

Connect in Telara

Multiple fields

In Telara, open Settings → Integrations, choose this connector, and complete the fields Telara shows.

Fields Telara asks for

API key
App Key

OAuth 2.0

OAuth2 with PKCE (access_token used as DD-API-KEY)

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Knowledge

What gets indexed

Resource	Coverage
Dashboard	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Dashboard	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Dashboard.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Site selection matters (US1 vs EU). The wrong site looks like a bad key.

Keys inherit the privileges of the creating user; a narrowly privileged user yields a narrow view in Telara.