Connecting DataDog - AWS DevOps Agent
Built-in, 1 way integrationOnboardingRemoval

Connecting DataDog

Built-in, 1 way integration

Currently, AWS DevOps Agent supports Datadog users with built-in, 1 way integration, enabling the following:

  • Automated Investigation triggering - Datadog events can be configured to trigger AWS DevOps Agent incident resolution Investigations via AWS DevOps Agent webhooks.

  • Telemetry introspection - AWS DevOps Agent can introspect Datadog telemetry as it investigates an issue via the each providers remote MCP server.

Onboarding

Step 1: Connect

Establish connection to your Datadog remote MCP endpoint with account access credentials

Configuration

  1. Open the hamburger menu and select Settings

  2. Scroll to the Available - Telemetry section. Press Register next to Datadog

  3. Enter your Datadog MCP server details:

  4. Click Next

  5. Review and submit

Authorization

Complete OAuth authorization by:

  • Authorizing as your user on the Datadog OAuth page

  • If not logged in, click Allow, login, then authorize

Once configured, Datadog becomes available across all Agent spaces.

Step 2: Enable

Activate DataDog in a specific Agent space and configure appropriate scoping

Configuration

  1. From the agent spaces page, select an agent space and press view details (if you have not yet created an agent space see Creating an Agent Space)

  2. Select the Capabilities tab

  3. Scroll down to the Telemetry section

  4. Press Add

  5. Select Datadog

  6. Next

  7. Review and press Save

  8. Copy the Webhook URL and API Key

Step 3: Configure webhooks

Using the Webhook URL and API Key you can configure Datadog to send events to trigger an investigation, for example from an alarm.

To ensure that events sent can be used by the DevOps Agent, make sure that the data transmitted to the webhook matches the data schema specified below. Events that do not match this schema may be ignored by DevOps Agent.

Set the method and the headers

    method: "POST",
    headers: {
      "Content-Type": "application/json",
      "Authorization": "Bearer <Token>",
    },
    

Send the body as a JSON string.

{
    eventType: 'incident';
    incidentId: string;
    action: 'created' | 'updated' | 'closed' | 'resolved';
    priority: "CRITICAL" | "HIGH" | "MEDIUM" | "LOW" | "MINIMAL";
    title: string;
    description?: string;
    timestamp?: string;
    service?: string;
    // The original event generated by service is attached here.
    data?: object;
}

Send webhooks with Datadog https://docs.datadoghq.com/integrations/webhooks/ (note select no authorization and instead use the custom header option).

Learn more: Datadog Remote MCP Server

Removal

The telemetry source is connected at two levels at the agent space level and at account level. To completely remove it you must first remove from all agentspaces where it is used and then it can be unregistered.

Step 1: Remove from agent space

  1. From the agent spaces page, select an agent space and press view details

  2. Select the Capabilities tab

  3. Scroll down to the Telemetry section

  4. Select Datadog

  5. Press remove

Step 2: Remove from agent space

  1. Open the hamburger menu and select Settings

  2. Scroll to the Currently registered section.

  3. Check the agent space count is zero (if not repeat Step 1 above in your other agent spaces)

  4. Press Deregister next to Datadog