​
Authentication

This provider requires authentication.

  • api_key: Datadog Api Key (required: True, sensitive: True)
  • app_key: Datadog App Key (required: True, sensitive: True)
  • domain: Datadog API domain (required: False, sensitive: False)
  • environment: Topology environment name (required: False, sensitive: False)
  • oauth_token: For OAuth flow (required: False, sensitive: True)

Certain scopes may be required to perform specific actions or queries via the provider. Below is a summary of relevant scopes and their use cases:

  • events_read: Read events data. (mandatory)
  • monitors_read: Read monitors (mandatory) (Documentation)
  • monitors_write: Write monitors (Documentation)
  • create_webhooks: Create webhooks integrations
  • metrics_read: View custom metrics.
  • logs_read: Read log data.
  • apm_read: Read APM data for Topology creation.
  • apm_service_catalog_read: Read APM service catalog for Topology creation.

​
In workflows

This provider can be used in workflows.

As “step” to query data, example:

steps:
    - name: Query datadog
      provider: datadog
      config: "{{ provider.my_provider_name }}"
      with:
        query: {value}  
        timeframe: {value}  
        query_type: {value}

Check the following workflow examples:

​
Topology

This provider pulls topology to Keep. It could be used in correlations and mapping, and as a context for alerts and incidents.

​
Provider Methods

The provider exposes the following Provider Methods. They are available in the AI Assistant.

  • mute_monitor Mute a monitor (action, scopes: monitors_write)

  • unmute_monitor Unmute a monitor (action, scopes: monitors_write)

  • get_monitor_events Get all events related to this monitor (view, scopes: events_read)

  • get_trace Get trace by ID (view, scopes: apm_read)

  • create_incident Create an incident (action, scopes: incidents_write)

  • resolve_incident Resolve an active incident (action, scopes: incidents_write)

  • add_incident_timeline_note Add a note to an incident timeline (action, scopes: incidents_write)

​
Connecting with the Provider

​
API Key

To obtain the Datadog API key, follow these steps:

  1. Log in to your Datadog account.
  2. Navigate to the “Integrations” section.
  3. Click on the “API” tab.
  4. Generate a new API Key.

​
App Key

To obtain the Datadog App Key, follow these steps:

  1. Log in to your Datadog account.
  2. Navigate to the “Integrations” section.
  3. Click on the “API” tab.
  4. Generate a new App Key or use an existing one.

​
Fingerprinting

Fingerprints in Datadog are calculated based on the groups and monitor_id fields of an incoming/pulled event.

​
Notes

No information yet, feel free to contribute it using the “Edit this page” link at the bottom of the page

​
Webhook Integration Modifications

The webhook integration adds Keep as a monitor within Datadog. It can be found under the “Monitors” section. The integration automatically gains access to the following scopes within Datadog:

  • monitors_read
  • monitors_write
  • create_webhooks