Datadog integration ►

This integration ingests Datadog metrics and events into Moogsoft. The ingestion engine performs anomaly detection on all metrics and generates events for detected anomalies.

The Datadog metric polling rate is 1 minute (rate limited) and the event polling rate is 30 seconds (not rate limited). To avoid rate limiting, you can configure your integrations to ensure that Datadog pushes relevant metrics and events only. For more information, search for "API rate limits" in the Datadog documentation.

This integration was validated in Datadog on August 17, 2021. See the Datadog documentation for details on Datadog components.

Best practices

  • It is good practice to ingest CloudWatch data directly using the AWS CloudWatch Integration rather than via Datadog. Ingesting CloudWatch data collected via Datadog can introduce latencies in the CloudWatch data.

  • To avoid rate limiting, and to ensure that Datadog pushes data of interest only, it is good practice to include event and metric filters as described below.

Obtain your API key and Application key in Datadog

Log in to Datadog and do the following:

  1. Go to Team (left menu) > Application Keys (top menu) and then click New Key (right).

  2. Enter a name for the key and click Create Key.

  3. Copy the KEY to a text file.

  4. Next, in Datadog, go to Integrations > APIs and click on API Keys.

  5. In the New API Key field, enter a name and click Create API Key.

  6. Copy the API Key value when it generates.

Set up the Integration in Moogsoft

  1. Go to Data Config > Ingestion Services > Datadog and create a new integration.

  2. Enter the Name and the Credentials for the integration. If you do not have a profile defined, click Add New Credentials and enter your Application Key and API Key from Datadog.

  3. Under Collect Datadog Events, set up the filters to specify the events that you want Datadog to push. Datadog pushes only events that match all of the specified filters.

    1. Datadog Priority — An event must have a Low or Normal priority. If no filter is defined, Datadog does not filter based on priority.

    2. Datadog Hosts — An event must come from a source in this list. The list is preconfigured based on your Datadog instance. Delete any Datadog monitoring sources that you do not want to ingest.

    3. Datadog Tags — An event must contain all specified tags. To add a tag, enter the tag string and press Enter. You can also select host tags from the pull-down menu. It is good practice to review your event tags in Datadog and verify that this list includes all relevant tags and excludes all irrelevant tags.  If no filter is defined, Datadog considers all tags.

  4. Under Collect Datadog Metrics, set up the filters to specify the metrics that you want Datadog to push. Datadog pushes only metrics that match all of the specified filters.

    • Datadog Metric Name —A metric must have a name in this list. If no filter is defined, Datadog considers all metric names.

    • Datadog Host —A metric must come from a source in this list. The list is preconfigured based on your Datadog instance. Delete any Datadog monitoring sources that you do not want to ingest.

    • Datadog Tag Filter — A metric must contain all specified tags. To add a tag, enter the tag string and press Enter. You can also select host tags from the pull-down menu. It is good practice to review your metric tags in Datadog and verify that this list includes all relevant tags and excludes all irrelevant tags. If no filter is defined, Datadog considers all tags.

The UI shows the integration status after setup. The status can be one of the following:

  • Starting - The integration is scheduled to begin polling for data from Datadog.

  • Running - integration is polling Datadog successfully.

  • Disconnected -- The integration was disconnected due to credential issues. Confirm your Credentials Store definition has the correct Datadog API and application keys.

  • Limited -- Datadog has stopped pushing data due to hourly polling limits. If you see this, consider refining your event or metric filters to reduce the amount of data getting pushed.

  • Stopped -- The integration stopped running due to an internal issue.

You do not need to perform any integration-specific steps on your Datadog systems. After you set up the integration, it polls each Datadog endpoint at regular intervals to collect metrics and events.

2021-10-18T23:55:05+01:00