RunReveal

Datadog Audit Trail

Datadog Audit Trail captures a record of every action taken by users and administrators in your Datadog organization — including dashboard and monitor changes, authentication events, API key management, user administration, and configuration updates across all Datadog products.

RunReveal polls the Datadog Audit Logs API every 60 seconds and will backfill up to 30 days of events on first connect.

Ingest Methods

API Polling

Setup

  1. Go to Sources in RunReveal
  2. Click the Datadog Audit Trail source tile
  3. Give it a name
  4. Select your Datadog Site (the regional endpoint your organization uses)
  5. Enter your API Key and Application Key, then click Connect Source

Datadog Site

Datadog operates multiple regional sites. Select the one that matches your organization's Datadog account:

SiteURL
US1 (default)datadoghq.com
US3us3.datadoghq.com
US5us5.datadoghq.com
EU1datadoghq.eu
AP1ap1.datadoghq.com
AP2ap2.datadoghq.com
US1-FEDddog-gov.com

If you're unsure which site your organization uses, check the URL you use to log in to Datadog — it will contain the site domain.

API Key

  1. In Datadog, navigate to Organization Settings → API Keys
  2. Click New Key, give it a descriptive name (e.g., RunReveal), and copy the key value

Application Key

The Application Key authorizes RunReveal to read audit events. The key inherits the permissions of the user or service account it belongs to, so that account must have the Audit Logs Read permission.

  1. In Datadog, navigate to Organization Settings → Application Keys
  2. Click New Key, give it a descriptive name (e.g., RunReveal Audit), and copy the key value

Permission Required: The Application Key's owner must have the audit_logs_read permission. If you see authorization errors after connecting, verify the key owner has this permission under Organization Settings → Roles.

Least Privilege: For security, create a dedicated service account with only the audit_logs_read permission and generate the Application Key from that account rather than a personal account.

Verify It's Working

Once added, logs should begin flowing within a minute. Validate with:

SELECT * FROM datadog_audit_logs LIMIT 1

Event Types Collected

Datadog Audit Trail covers a broad range of organizational activity:

  • Authentication — User logins, API key usage, session events
  • Dashboards — Create, update, and delete actions
  • Monitors — Alert configuration changes
  • API & Application Keys — Key creation, rotation, and deletion
  • User Management — Invitations, role changes, team membership updates
  • Notebooks & Logs — Configuration and pipeline changes
  • Integrations — Third-party integration changes
  • Settings — Organization-wide configuration updates

Schema

The following columns are exposed for this source. RunReveal applies schema normalization across all sources, ensuring uniform field names and data types for cross-source queries and reusable detection logic.

Table: datadog_audit_logs (51 columns)

ColumnType
workspaceIDString
sourceIDString
sourceTypeString
sourceTTLUInt32
receivedAtDateTime
idString
eventTimeDateTime
eventNameString
eventIDString
srcIPString
srcASCountryCodeString
srcASNumberUInt32
srcASOrganizationString
srcCityString
srcConnectionTypeString
srcISPString
srcLatitudeFloat64
srcLongitudeFloat64
srcUserTypeString
dstIPString
dstASCountryCodeString
dstASNumberUInt32
dstASOrganizationString
dstCityString
dstConnectionTypeString
dstISPString
ColumnType
dstLatitudeFloat64
dstLongitudeFloat64
dstUserTypeString
actorMap(String, String)
tagsMap(String, String)
resourcesArray(String)
serviceNameString
enrichmentsArray(Tuple(data Map(String, String), name String, provider String, type String, value String))
readOnlyBool
rawLogString
ddEventIDString
ddServiceString
ddMessageString
ddEvtNameString
ddEvtCategoryString
ddEvtOutcomeString
ddUsrEmailString
ddUsrIDString
ddUsrNameString
ddClientIPString
ddHTTPMethodString
ddHTTPStatusCodeString

On this page