New Relic Alerts Integration Guide

New Relic is an all-in-one server and web application performance tool that lets you see performance from the end user experience down to the line of application code. Combining real user monitoring, application monitoring, and availability monitoring in a single solution built from the ground up, New Relic lets developers and operations teams manage web application performance in real-time.

Existing PagerDuty customers get New Relic Lite for free! Getting started only takes a few minutes. Just head over to New Relic and sign up for an account.

This guide covers the steps to integrate New Relic’s new Alerts system with PagerDuty. If you are using the basic alerting system at, you will want to follow our New Relic Legacy Alerting Integration Guide instead.

In PagerDuty

    1. From the Configuration menu, select Services. 
    2. On your Services page:

      If you are creating a new service for your integration, click +Add New Service.

      If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +New Integration button.

    3. RS-Add-New-Service

    4. Select your app from the Integration Type menu and enter an Integration Name.

      If you are creating a new service for your integration, in General Settings, enter a Name for your new service. Then, in Incident Settings, specify the Escalation Policy, Notification Urgency, and Incident Behavior for your new service.

    5. Click the Add Service or Add Integration button to save your new integration. You will be redirected to the Integrations page for your service.
    6. Copy the Integration Key for your new integration: RS_API_pd_3

    In New Relic

    1. Go to Alerts New, click Notification Channels, go to the Channels tab, then click New notification channel.

    2. Select PagerDuty from the Channel type menu. Give your channel a Service name, then paste the Integration Key you copied in step 3 above in to the Service API key field and click Create channel.

    3. Click Send a test notification to verify your integration key was entered correctly and an incident is triggered in PagerDuty, then click Got it.

      If you do not see an incident triggered in PagerDuty, check the response for errors and make sure somebody is on-call for your service.

    4. After the channel is created, go to the Alert policies tab and click Add alert policies.

    5. Check the alert policies you want to trigger incidents in PagerDuty, then click Save changes.

    6. Congratulations! New Relic will now be able to trigger and resolve incidents in PagerDuty.

      If you experience any issues outside of PagerDuty you’ll want to be sure to report them to New Relic since this is a new system and they’ll need to know about any problem you experience in order to fix them.


    Can you associate New Relic with more than one PagerDuty service?

    Yes, you can tie New Relic to multiple PagerDuty services by creating additional services in PagerDuty and additional channels in New Relic which use different PagerDuty Service Integration Keys. This is extremely useful for dividing your alerts up to different escalation policies so that the proper team is notified for incidents relevant to them.