Datadog support

Last updated date:

Connect, reconnect, and troubleshoot Datadog without sharing credentials or customer content through support channels.

1. Before you start

  • Identify the account's exact Datadog site, such as datadoghq.com, datadoghq.eu, an approved regional site, or ddog-gov.com.
  • Create or select the organization API key and a dedicated scoped application key.
  • Grant only monitors_read, dashboards_read, slos_read, incident_read, apm_service_catalog_read, user_access_read, teams_read, restriction_policies_read, and audit_logs_read.
  • Do not send Datadog credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Datadog API and application keysDatadog's API and application-key administration guidance.

2. Connect Datadog

  1. In Seedling, open Connections and choose Datadog.
  2. Choose personal or workspace scope deliberately; Seedling never promotes an actor-owned connection into workspace access.
  3. Enter the API key, scoped application key, exact Datadog site, and an API base URL only when it is a Datadog API host.
  4. Seedling validates the key pair and site, verifies released resource families, and rejects a site/account mismatch.
  5. Allow the first Datadog synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Datadog key pair rejected
Confirm the datadog key pair is active, was entered without surrounding whitespace, and belongs to the intended Datadog account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Datadog population as empty.
Wrong account or scope
Disconnect before retrying with the intended Datadog identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the connection uses the Datadog site that owns the organization and keys.
  2. Check the application key's resource scope and the owning user's current role or service-account status.
  3. Confirm the missing monitor, incident, service, dashboard, notebook, or audit event remains within provider retention and visibility.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement datadog key pair for the same Datadog account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old datadog key pair in Datadog.