New Relic Integration

New Relic Integration

Overview

The New Relic integration connects your New Relic observability platform with Overwatch through workflow webhook notifications. When New Relic detects alert conditions, it sends structured payloads containing entity data, condition details, and policy information. Overwatch parses these payloads, maps entity types to infrastructure context, and creates incidents with full diagnostic information.

Overwatch automatically identifies entity types (service, host, application) from New Relic’s entity model and extracts Kubernetes, AWS, and application tags for AI-powered root cause analysis.

Prerequisites

• A New Relic account with alert workflow configuration permissions
• An Overwatch organization with an active subscription
• The integration ID from your Overwatch Settings page
• (Optional) A webhook signing secret for X-NewRelic-Signature validation

Setup Steps

1. In Overwatch, navigate to Settings > Integrations > New Integration and select New Relic.
2. Copy the generated Integration ID and the full webhook URL:

   https://your-overwatch-instance/api/v1/webhooks/newrelic/{integration_id}

3. In New Relic, navigate to Alerts & AI > Workflows > Create Workflow.
4. Configure a destination:
   • Select Webhook as the destination type
   • Endpoint URL: Paste the webhook URL from step 2
   • Headers: Add X-NewRelic-Signature with your signing secret if you configured one in Overwatch
5. Choose which alert conditions or policies should trigger notifications to Overwatch.
6. Save the workflow.
7. In Overwatch, click Test Connection to verify the integration.

Tip: Use New Relic’s workflow enrichment feature to include additional entity data in the webhook payload. The more context you send, the more accurate Overwatch’s AI analysis becomes.

Alert Format

Overwatch extracts the following fields from New Relic workflow payloads:

Field	Source	Description
issueId	issueId	New Relic issue identifier
entity_guid	entity.guid	Unique entity identifier
entity_name	entity.name	Entity display name
entity_type	entity.type	Entity classification (service, host, application)
entity_domain	entity.domain	Entity domain (APM, INFRA, BROWSER, MOBILE)
conditionName	conditionName	Alert condition that triggered
policyName	policyName	Alert policy name
priority	priority	Alert priority level
state	state	Alert state (ACTIVATED, CLOSED)

Entity type mapping: Overwatch maps New Relic entity types to infrastructure identifiers:

• service or apm entities map to service_name
• host or infrastructure entities map to host_name
• application entities map to application_name

Entity tags: Overwatch also extracts context from New Relic entity tags, including:

• AWS tags: aws.region, aws.accountId
• Kubernetes tags: clusterName, namespaceName, podName, containerName, deploymentName
• Environment tags: environment, hostname
• Application tags: appName, language, framework

Chrome Extension Detection

The Overwatch Chrome extension activates on:

• one.newrelic.com

When you view an entity or alert in New Relic that matches an active Overwatch incident, the extension panel displays AI-generated resolution steps, related incidents, and links to relevant runbooks.

Troubleshooting

Webhook not receiving alerts

• Verify the webhook URL is correctly configured in the New Relic workflow destination.
• Confirm the workflow is active and associated with the correct alert policies or conditions.
• Check the New Relic Workflows > Activity tab for delivery status and error messages.

Signature validation failures

• Ensure the secret configured in Overwatch matches the one used to generate the X-NewRelic-Signature header.
• If signature validation is not required, you can leave the webhook secret field empty in Overwatch.

Missing entity context

• Overwatch depends on entity tags for infrastructure mapping. Ensure your New Relic entities have tags like environment, clusterName, and aws.region applied.
• Use New Relic’s tag management to add missing tags to entities.

Incidents not mapping to services

• Check that the entity type in the webhook payload is recognized. Overwatch maps service, apm, host, infrastructure, and application entity types automatically.
• For custom entity types, the entity name is stored as a custom variable and still available for AI analysis.