For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
13.5kProductPricingSign inStart free trialBook a demo
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
    • Home
  • Get started
    • Quickstart
    • Introduction to feature flags
    • Unleash architecture overview
  • Core concepts
    • Overview
    • Import and export
      • Unleash hosting options
        • Integrations overview
        • Datadog
        • Slack
        • Microsoft Teams
        • Terraform
        • Webhook
      • Developer Toolbar

Unleash reduces the risk of releasing new features, drives innovation by streamlining the software release process, and increases revenue by optimizing end-user experience. While we serve the needs of the world's largest, most security-conscious organizations, we are also rated the “Easiest Feature Management system to use” by G2.

GitHubGitHubLinkedInLinkedInX (Twitter)X (Twitter)SlackSlackStack OverflowStack OverflowYouTubeYouTube

Server SDKs

  • Node.js
  • Java
  • Go
  • Rust
  • Ruby
  • Python
  • .NET
  • PHP
  • All SDKs

Frontend SDKs

  • JavaScript
  • React
  • Next.js
  • Vue
  • iOS
  • Android
  • Flutter

Feature Flag use cases

  • Secure, scalable feature flags
  • Rollbacks
  • FedRAMP, SOC2, ISO2700 compliance
  • Progressive or gradual rollouts
  • Trunk-based development
  • Software kill switches
  • A/B testing
  • Feature management
  • Canary releases

Product

  • Quickstart
  • Unleash architecture
  • Pricing
  • Product vision
  • Open live demo
  • Open source
  • Enterprise feature management platform
  • Unleash vs LaunchDarkly

Support

  • Help center
  • Status
  • Changelog
Made in a cosy atmosphere in the Nordic countries.Copyright © 2026 Unleash
LogoLogo
13.5kProductPricingSign inStart free trialBook a demo
On this page
  • Configuration
Integrate and deployIntegrations

Datadog

||View as Markdown|
Was this page helpful?

Last updated May 11, 2026

Previous

Jira Cloud Integration - Installation

Next
Built with
v4.0

The Datadog integration allows Unleash to post Updates to Datadog when a feature flag is updated. To set up this integration, you need to set up a webhook connector for your channel. You can follow Submitting events to Datadog on how to do that.

The Datadog integration will perform a single retry if the HTTP POST against the Datadog Webhook URL fails (either a 50x or network error). Duplicate events may happen, and you should never assume events always comes in order.

Configuration

Events

You can choose to trigger updates for the following events:

  • feature-created
  • feature-metadata-updated
  • feature-project-change
  • feature-archived
  • feature-revived
  • feature-strategy-update
  • feature-strategy-add
  • feature-strategy-remove
  • feature-stale-on
  • feature-stale-off
  • feature-environment-enabled
  • feature-environment-disabled
  • feature-environment-variants-updated
  • feature-potentially-stale-on
  • feature-updated (deprecated in v4.3)

Parameters

Unleash Datadog integration takes the following parameters.

  • Datadog Events URL - This is an optional property. The default URL is https://api.datadoghq.com/api/v1/events. If you are not not using the US1 Datadog site, you’ll need to change this. Some instances and their URLs are:

    • EU: https://app.datadoghq.eu/api/v1/events
    • US1: https://app.datadoghq.com/api/v1/events
    • US3: https://us3.datadoghq.com/api/v1/events
    • US1-FED: https://app.ddog-gov.com/api/v1/events
  • Datadog API key - This is a required property. The API key to use to authenticate with Datadog.

  • Datadog Source Type Name - This is an optional property. Sets source_type_name parameter to be included in Datadog events. List of valid api source values

  • Extra HTTP Headers - This is an optional property. Used to set the additional headers when Unleash communicates with Datadog.

Example:

1{
2 "SOME_CUSTOM_HTTP_HEADER": "SOME_VALUE",
3 "SOME_OTHER_CUSTOM_HTTP_HEADER": "SOME_OTHER_VALUE"
4}

Body template availability

The body template property is available from Unleash 5.6 onwards.

  • Body template - This is an optional property. The template is used to override the body template used by Unleash when performing the HTTP POST. You can format your message using a Mustache template. Refer to the Unleash event types reference to find out which event properties you have access to in the template.

Example:

1{
2 "event": "{{event.type}}",
3 "createdBy": "{{event.createdBy}}",
4 "featureToggle": "{{event.data.name}}",
5 "timestamp": "{{event.data.createdAt}}"
6}

If you don’t specify anything Unleash will send a formatted markdown body.

Example:

1username created feature flag (featurename)[http://your.url/projects/projectname/features/featurename] in project *projectname*

Tags

Datadog’s incoming webhooks are app specific. You will be able to create multiple integrations to support messaging on different apps.