Datadog

Introduction

A Datadog integration marks every experiment run in Datadog: a marker when a run starts, when its split changes, when a variation is shipped and when the run is stopped. The markers land next to the metrics the run is meant to move. You set this up in the dashboard, with no code.

The marker is a change event in Datadog's event stream and on dashboards that show events, tagged source:configdirector, config:<key> and environment:<slug>, with the config as the changed feature flag and the member as the author.

Settings

Create the integration

1. Open Integrations at the bottom of the dashboard's navigation and pick the tool, or click Add integration when you already have one.
2. Give the integration a name, or keep the tool's name.
3. Fill in the settings above and paste the credential you created in the tool. Credentials are stored encrypted and never shown again.
4. Narrow it down with the Projects, Environments and Tags filters, or leave them empty to mark every run. A run is marked when its project, its environment and its config's tags pass every filter you set; an empty filter lets everything through. An integration filtered to Production marks Production runs only.
5. Keep Enabled on. A disabled integration marks nothing, and runs that start or end while it is disabled are not marked later.
6. Save. The integration's page shows the tool's settings and the address it posts to.
7. Click Send test marker and confirm. A marker titled ConfigDirector test is posted to the tool right away, at the current time, and shows under Deliveries with the tool's response, so you can see where run markers will land.

The Analytics overview explains what each marker says, how deliveries are retried and what happens when the tool stops accepting markers.

What ConfigDirector posts

The integration posts to https://event-management-intake.{site}/api/v2/events with the key in the DD-API-KEY header. Set an endpoint URL under Advanced only to post somewhere else.

Datadog's documentation: Post an event.