Skip to main content
The New Relic integration connects Rootly with your New Relic account in two directions. New Relic alert policies send issue events into Rootly as alerts, and incident workflows capture chart snapshots so responders keep point-in-time visibility into your observability data without leaving the incident. With the New Relic integration, you can:
  • Receive New Relic issue events as Rootly alerts
  • Filter and route alerts using workflow conditions on fields like priority, state, and workflowName
  • Capture New Relic chart snapshots from Genius workflows during incidents
  • Attach snapshot links to incident timelines for post-incident review

​
Before You Begin

Before setting up the integration, make sure you have:
  • A Rootly account with permission to manage integrations
  • A New Relic account with permission to create API keys
  • Your New Relic Account ID
  • Access to configure notification channels in New Relic, if you plan to ingest alerts
Rootly recommends integrating with a dedicated service account so the integration does not break if an individual user leaves your organization.

​
Installation

Open the New Relic integration in Rootly

Navigate to the integrations page in Rootly and select New Relic.
New Relic integration on the integrations page

Generate a New Relic API key

In New Relic, navigate to your API keys settings.
New Relic API keys page
New Relic API key list
Generate a new User key and copy it.
Generate New Relic API key
Copy the API key immediately after generating it — New Relic will not show the full key again.

Enter your credentials in Rootly

Paste your API key and Account ID into the New Relic integration settings in Rootly and save.
Enter New Relic credentials in Rootly

​
Ingest New Relic Alerts

New Relic sends alert events into Rootly through a webhook notification channel. Once alerts are flowing, alert workflows can create incidents, notify Slack channels, or page on-call targets.
Install the integration before setting up the webhook. The bearer token is generated during installation and is required for authentication.

​
Configure a Webhook in New Relic

Open notification channels in New Relic

In New Relic, navigate to Alerts > Notification channels and create a new channel.
New Relic notification channels page

Create a Rootly webhook channel

Select Webhook as the channel type and configure it with the following values:
  • Webhook URL: https://webhooks.rootly.com/webhooks/incoming/new_relic_webhooks
  • Auth type: Bearer token
  • Token: the bearer token shown in your Rootly New Relic integration settings
New Relic webhook channel configuration
New Relic webhook bearer token field
Your bearer token is available in Rootly under Integrations > New Relic > Configure.
Bearer token in Rootly integration settings

Test the webhook

Click Test Notification in New Relic. A test alert should appear on your Rootly Alerts page.
Test alert appearing in Rootly
If the test alert appears in Rootly, the integration is working correctly. You can now attach this channel to New Relic alert policies.

​
How Alerts Are Mapped

Rootly extracts the following fields from each New Relic alert payload:
  • Summary — the title field from the New Relic issue
  • External ID — the issue id, used to deduplicate alerts
  • External URL — the issueUrl, linking back to the New Relic issue
  • Labels — state, trigger, priority, and workflowName are attached as Rootly alert labels
New Relic priority and state values are available as alert labels in Rootly. You can use these in workflow run conditions to handle critical vs warning alerts differently.

​
Workflow Actions

Once the integration is connected, a new task is available in your Genius workflows to capture New Relic chart snapshots during incidents.
New Relic snapshot task in Genius workflows
Snapshots are point-in-time captures attached to the incident timeline, so you can reference exactly what your metrics looked like when the incident occurred.

​
Troubleshooting

Verify that the webhook URL and bearer token are correct. Use the Test Notification button in New Relic to confirm delivery. Ensure the notification channel is attached to the alert policy that fired.
Rootly extracts fields from the standard New Relic issue payload. If your New Relic account uses a customized payload template for the webhook channel, ensure it still includes the standard fields: title, id, issueUrl, state, priority, and createdAt.
Confirm you are using the token from the Rootly New Relic integration settings, not your New Relic API key. These are different credentials — the bearer token is generated by Rootly for authenticating inbound webhooks.

​
Uninstall

To remove the New Relic integration, open the integrations panel in Rootly and select Configure > Delete.