Datadog
Monitoring · API key / service-account token · Daily
API key + read-only Application key. Pulls active-monitor posture and log-alert monitor presence for system-monitoring (SI-4) and automated audit-record analysis (AU-6) evidence.
- Authentication
- API key / service-account token
- Sync cadence
- Daily
- Stale threshold
- Every 2 days
- Category
- Monitoring
Evidence this connector produces
Every sync writes typed evidence rows linked to the controls below. Evidence is immutable once attached to an approved assessment, fingerprinted for de-dup, and surfaced in the control coverage calculation on your dashboard.
How to connect
Create an API key and a read-only Application key in Datadog, pick your site, and paste all three.
- 1Create the API key
Datadog → Organization Settings → API Keys → New Key.
- 2Create the Application key
Organization Settings → Application Keys → New Key. Scope it to a read-only role (monitors_read is sufficient).
- 3Note your site
Your Datadog URL tells you the site: app.datadoghq.com → datadoghq.com; app.datadoghq.eu → datadoghq.eu; us3/us5/ap1 subdomains map to their sites.
Security model
Every connector ships behind the same auditor-grade primitives — not just RBAC config, but architectural enforcement.
Tokens, client secrets, and service-account keys are encrypted under a per-tenant AWS KMS data key. The plaintext is never persisted, never logged, and never leaves the FastAPI process boundary.
Every Connection, ConnectorRun, and emitted Evidence row carries an organization ObjectId. The scheduler never iterates without an org-scoped filter; cross-tenant evidence bleed is impossible at the data layer.
Connect, sync, sync-failure, re-auth, and revoke each write a row to the immutable AuditLog. The full lifecycle is reconstructable for any examiner.
Revoking a connection sets deletedAt and clears the encrypted credential blob, but the historical evidence + sync log stays queryable for the retention window. Auditors can still trace what was attested when.
If this connector hasn't synced in Every 2 days, control coverage degrades automatically and an alert fires. Auditors don't trust stale evidence — neither do we.
We request the minimum read-only scopes needed for the listed evidence. No write scopes, no admin scopes, no scopes outside the documented set.
Ready to connect Datadog?
Connect from Settings → Integrations — typically under 5 minutes. Or talk to us first.