Datadog

Datadog context enriches an existing Pulse. It does not create Pulses.

How this helps triage: matching excerpts can show up in the summary, the first checks, and What informed this on the Pulse.

Exhale uses a Datadog API key at triage time to attach service, monitor, and event excerpts. An optional application key enables recent Events API enrichment; an API key alone still contributes a connected-site excerpt.

This is not monitor webhook ingest. If Datadog monitors should become Pulses, connect Sources → Datadog.

Connect

1. Sign in as a workspace admin.
2. Open Connections → Context → Observability context → Datadog.
3. Save the API key (and optional application key), then Test connection.
4. Test connection to mark the connector configured.

See Datadog's official guide: API and Application Keys.

Missing credentials, timeouts, or vendor 403s skip this block. Triage still completes. Send-test-alert Pulses skip live collectors.

Plan

Datadog Context is available on all plans.

Connector slots are shared across Context categories (markdown runbooks use a separate document cap). Tighten AI → Prompt → Context use if excerpts are noisy or too large.

API

Writes use the signed-in session and CSRF. Secrets are never returned on GET.

Related log or trace lines and deep links attach when keys have the needed scopes.

Related

• Context index
• Prompt → Context use