Cloud

Connect Datadog

Reads Datadog monitors, SLOs, incidents, and optional usage cost summaries to feed Delivery Health and Cloud Health from aggregate observability signals.

What you'll need

A Datadog API key, application key, and site. The connector only performs read calls and stores aggregate counts, SLO percentages, incident MTTA/MTTR, and cost totals.

Credential

API key + read-scoped application key

Requested scopes

monitors_read, slos_read, incidents_read, usage_read

Powers

Delivery Health, Cloud Health

What it pulls

Current user validation, one bounded page of monitors and SLOs, bounded 30-day incidents, and optional usage-cost summaries. Licensed or unavailable endpoints are omitted rather than treated as clean.

What you’ll enter

The exact fields the connect form asks for — and where to find each value.

Datadog siteoptional: Your Datadog site (for example us1, eu, us3, us5, ap1, ap2, or api.datadoghq.eu). Leave blank for us1.
API key: Datadog → Organization Settings → API Keys. The connector only uses read endpoints.
Application key: Datadog → Organization Settings → Application Keys. Grant read access for monitors, SLOs, incidents, and usage where available.

Step-by-step setup

1
Choose your site
Use your Datadog site such as us1, eu, us3, us5, ap1, ap2, or the full api host.
2
Create read keys
Create an API key and an application key with read access for monitors, SLOs, incidents, and usage where available.
3
Connect
Paste the site, API key, and application key, then click Connect. We validate current-user access and sync aggregate observability signals.

Create Datadog keys → Connect in the app

Read-only adapter implemented with mocked-fetch coverage; full production confidence requires connecting customer read credentials.