Connecting New Relic - AWS DevOps Agent
Built-in, 1 way integrationOnboardingRemoval

Connecting New Relic

Built-in, 1 way integration

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

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

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

Onboarding

Step 1: Connect

Establish connection to your New Relic 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 New Relic

  3. Follow the instructions to obtain your New Relic API Key

  4. Enter your New Relic MCP server API Key details:

    • Account ID: - Enter your New Relic account ID obtained above

    • API Key: Enter the API Key obtained above

    • Select US or EU region based on where your New Relic account is.

  5. Click Add

Step 2: Enable

Activate New Relic 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 New Relic

  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 New Relic 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 New Relic https://newrelic.com/instant-observability/webhook-notifications (note select no authorization and instead use the custom header option)

Learn more: https://docs.newrelic.com/docs/agentic-ai/mcp/overview/

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 New Relic

  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 New Relic