Skip to main content
Connect DevHelm to Datadog to post incidents as Datadog Events. Each DevHelm incident event is delivered through the Datadog Events API v1 and shows up in your Event Stream and Event Explorer, where you can correlate it with metrics, build event monitors, and trigger workflows.

​
Setup

1

Create a Datadog API key

  1. In Datadog, open Organization Settings (click your avatar in the bottom-left)
  2. Under Access, go to API Keys
  3. Click New Key, give it a name, and copy the key
Use an API key, not an Application key. Events submitted to the Events API authenticate with the API key only — an Application key returns a 403.
2

Identify your Datadog site

Your site is the domain in your Datadog URL. DevHelm sends events to https://api.{site}/api/v1/events, so a wrong site causes 403s. If you’re on US1 you can omit site (it defaults to datadoghq.com).
Sitesite value
US1 (default)datadoghq.com
US3us3.datadoghq.com
US5us5.datadoghq.com
EU1datadoghq.eu
AP1ap1.datadoghq.com
US1-FEDddog-gov.com
3

Create the alert channel in DevHelm

devhelm alert-channels create \
  --name "Datadog Events" \
  --type datadog \
  --config '{"channelType":"datadog","apiKey":"your-datadog-api-key","site":"datadoghq.eu","tags":"service:api,env:production,team:platform"}'
4

Test the channel

devhelm alert-channels test <channel-id>

​
Configuration

FieldDescriptionRequired
apiKeyDatadog API key (not an Application key)Yes
siteDatadog site region; defaults to datadoghq.com (US1)No
tagsComma-separated tags attached to every event, e.g. service:api,env:productionNo

​
Tags

Tags you set in tags are attached to each event verbatim, so you can filter, group, and build event monitors in Datadog by service, env, team, and so on. DevHelm also auto-appends two tags per event:
  • monitor:<monitor name>
  • severity:<incident severity>

​
Troubleshooting

  1. Confirm you used an API key, not an Application key
  2. Verify the site matches your Datadog account region — an EU or US3/US5 account with the default datadoghq.com site will be rejected
  3. Check the key hasn’t been revoked in Organization Settings → API Keys
Events appear in the Event Explorer / Event Stream, not as metrics or logs. Search by source:devhelm or one of your configured tags. Note that the Events API accepts a submission with a 202 even before the event is indexed, so allow a few seconds.
Use Datadog’s key:value tag format and separate entries with commas, with no spaces around the commas — for example service:api,env:production. Free-form text without a colon is still accepted but is harder to filter on.