Observability & incidents
Datadog (API)
Connect a Datadog organization with an API key and a read-only application key.
Datadog connects with a key pair. Dave only reads.
Connect
Section titled “Connect”-
Note your site — the domain you see in the browser while using Datadog:
datadoghq.com(US1),us3.datadoghq.com,us5.datadoghq.com,datadoghq.eu(EU1),ap1.datadoghq.com,ap2.datadoghq.comorddog-gov.com(US1-FED). -
In Datadog, go to Organization Settings → API Keys and copy a key, or create one.
-
Go to Organization Settings → Application Keys → New Key, select the scopes under Permissions, and copy the key.
-
In Dave, go to Integrations → Add integration → Datadog (API).
-
Pick the Datadog site, then paste both keys. They are separate credentials — the API key identifies the organization, the application key carries the scopes — and both must belong to that site.
-
Set a Label — the name you will use to refer to this organization, e.g.
prod. -
Choose Connect Datadog.
Both keys are stored encrypted and never shown again.
Permissions
Section titled “Permissions”The API key has no scopes; it only identifies the organization.
The application key acts as the user who created it. Scope it explicitly: a key with no scopes inherits every permission that user has. Select these read scopes:
dashboards_readmonitors_readslos_readmetrics_readtimeseries_querylogs_read_datalogs_read_index_dataevents_readapm_readapm_service_catalog_readDave only sends read requests, so it never needs a write scope. The user creating the application key must hold these permissions too. Leave one out and Dave reports that part of Datadog as unavailable.
Creating an API key needs a Datadog role allowed to manage API keys, such as Datadog Admin. To keep the keys working when people leave, create the application key on a service account under Organization Settings → Service Accounts.
Manage the connection
Section titled “Manage the connection”In Datadog, on the site you sign in at:
- Organization Settings → API Keys — revoke the API key.
- Organization Settings → Application Keys — change the scopes or revoke the application key.
Disconnect in Dave stops Dave using the keys, but both stay active in Datadog until you revoke them there.
To rotate a key, Disconnect, then add the connection again with the same label and the new keys. Connect again only re-checks the keys Dave already has.
Troubleshooting
Section titled “Troubleshooting”- Datadog rejected the credentials. Check the site first: a key from one site does not authenticate against another. Then check both keys are still active.
- Validation takes long. Dave keeps retrying while Datadog is unreachable. Confirm the keys are still active in Datadog and belong to the selected site.