Configuring Datadog Integration

StatusDrift integrates with Datadog to send monitoring events to your observability platform. This guide explains how to configure the Datadog integration to correlate uptime data with your infrastructure metrics.

What This Integration Does

The Datadog integration sends events to your Datadog account when:

  • A monitored service goes down
  • A service recovers after an outage
  • Response time exceeds configured thresholds
  • SSL certificate issues are detected

These events appear in your Datadog Event Stream and can be used for dashboards, alerts, and correlation with other metrics.

Prerequisites

Before configuring the Datadog integration, ensure you have:

  • A Datadog account (Free tier or higher)
  • API key access in your Datadog account
  • Application key from your Datadog account (optional, but recommended)
  • A StatusDrift account with at least one monitor configured

Step 1: Get Your Datadog API Key

First, obtain an API key from your Datadog account:

  1. Log in to your Datadog account
  2. Navigate to Organization Settings > API Keys
  3. Click New Key
  4. Enter a name like “StatusDrift Integration”
  5. Click Create Key
  6. Copy the API key (you will not be able to see it again)

Step 2: Get Your Datadog Application Key (Optional)

While the API key handles sending events, an application key provides additional access for enhanced integration features. To obtain one:

  1. In your Datadog account, navigate to Organization Settings > Application Keys
  2. Click New Key
  3. Enter a name like “StatusDrift”
  4. Click Create Key
  5. Copy the application key and store it securely

Step 3: Add the Datadog Channel in StatusDrift

Now configure the integration in your StatusDrift dashboard:

  1. Log in to app.statusdrift.com
  2. Navigate to Notification Channels
  3. Click Add Channel
  4. Select Datadog from the channel type dropdown
  5. Enter a descriptive name for this channel
  6. Paste your Datadog API key
  7. Optionally, enter your Datadog application key
  8. Select your Datadog Site from the dropdown (defaults to US1)
  9. Optionally, add tags for event filtering (comma-separated, e.g., env:production, service:api)
  10. Click Create Channel
Datadog notification channel configuration form in StatusDrift showing API Key, Application Key, Site, and Tags fields
Datadog channel configuration in StatusDrift

Step 4: Assign to Monitors

Connect the notification channel to your monitors:

  1. Go to Monitors in your dashboard
  2. Select the monitor you want to connect
  3. In the Notification Channels section, enable your Datadog channel
  4. Save the monitor configuration
  5. Repeat for additional monitors as needed

Testing the Integration

Verify your Datadog integration is working:

  1. Go to Notification Channels in StatusDrift
  2. Find your Datadog channel
  3. Click the Test button
  4. Check your Datadog Event Stream for the test event

Configuration Options

The Datadog integration supports these configuration options:

FieldRequiredDescription
API KeyYesYour Datadog API key from Organization Settings > API Keys
Application KeyNoYour Datadog application key from Organization Settings > Application Keys
SiteYesYour Datadog site/region (US1, US3, US5, EU, AP1, AP2, or US1-FED)
TagsNoComma-separated tags to add to events (e.g., env:production, service:api)

Using StatusDrift Events in Datadog

Creating Dashboards

Use the Event Overlay widget to display StatusDrift events on your infrastructure dashboards, correlating outages with system metrics.

Setting Up Monitors

Create Datadog monitors that trigger based on StatusDrift events to integrate with your existing alerting workflows.

Troubleshooting

Events not appearing in Datadog

  • Verify your API key is correct and has not been revoked
  • Check that the channel is assigned to at least one monitor
  • Confirm you selected the correct Datadog site for your account
  • Look for error messages in your notification history

Events appearing with wrong tags

  • Review your tag configuration in StatusDrift
  • Ensure tags follow Datadog naming conventions

Was this article helpful?