Start free →

Datadog

Connecting Datadog lets an agent check that a change did not make things slower or noisier: latency, error rate, and whether any monitor went off after the deploy.

Before you start

You need a Datadog user with the mcp_read permission, plus the normal permissions for whatever the agent will read. Datadog's own guide is Set up the Datadog MCP Server.

Datadog's MCP server URL depends on your site. Open Datadog's setup guide and use the site selector on that page to get the endpoint for yours. Sites include app.datadoghq.com, us3.datadoghq.com, us5.datadoghq.com, app.datadoghq.eu, ap1.datadoghq.com, ap2.datadoghq.com and uk1.datadoghq.com.

You also need credentials. Either an access token, or an API key together with an application key. Create them in Datadog under your organization settings.

Connect it

  1. In SetForth, open your project, then Integrations.
  2. Choose Datadog.
  3. Enter the server URL for your Datadog site.
  4. Enter your credentials. For an access token, paste it as the token. For key pairs, add two headers: DD_API_KEY with your API key, and DD_APPLICATION_KEY with your application key.
  5. Choose Connect. SetForth tests the connection and reports the result.

What agents can check

Connecting an observability tool adds two follow-ups:

  • Hold latency budget blocks a merge when latency for the endpoints you name exceeds the budget you set. You choose the percentile and the budget in milliseconds.
  • No new alerts fails a task when its release fires a monitor that was quiet before. You choose which monitors count and the minimum severity.

You set the observation window when you add the follow-up during planning.