Skip to main content
OpenSRE queries Datadog during alert investigations — pulling logs, metrics, monitor state, and events correlated with incidents.

Prerequisites

  • Datadog account with API access
  • API key (organization settings)
  • Application key with read scopes (events_read, logs_read_data, logs_read_index_data, monitors_read)

Setup

Option 1: Interactive CLI

Or run the onboarding wizard and select Datadog. You will be prompted for API key, application key, and site (for example datadoghq.com or datadoghq.eu).

Option 2: Environment variables

Add to your .env:
For multiple Datadog orgs or sites, use multi-instance with DD_INSTANCES.

Option 3: Persistent store

Option 4: Hosted web app (OpenSRE Cloud)

In app.tracer.cloud, go to IntegrationsDatadog, enter a name, and paste your API and application keys.
Connect Datadog

Creating Datadog keys

API key

  1. In Datadog, go to Organization SettingsAPI Keys (direct link)
  2. Click + New Key and name it (for example opensre)
  3. Copy the key
Datadog API Key

Application key

  1. Go to User SettingsApplication Keys (direct link)
  2. Click + New Key and name it (for example opensre)
  3. Under Edit Scope, enable at minimum: events_read, logs_read_data, logs_read_index_data, monitors_read
  4. Under Actions API Access, click Enable
  5. Copy the key
Datadog App Key
Datadog App Key Scope
Some Datadog UI labels still say tracer from the Tracer→OpenSRE transition. Any key name works — use opensre for clarity.

Verify

Expected output:
Inside the REPL: /integrations verify datadog or /verify datadog.

Troubleshooting

Security best practices

  • Create a dedicated application key with read-only scopes for investigations.
  • Store keys in .env or your secret manager — not in source control.