New Relic Alerts Beta 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 Standard 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 Beta with PagerDuty. If you have not joined the New Relic Alerts Beta you will want to use our New Relic Legacy Alerting Integration Guide instead.

In PagerDuty

  1. Create a new Service by going to the Configuration menu and selecting Services, then click Add New Service.
  2. Enter a Name for your new service, select New Relic from the Integration Type menu, choose an Escalation Policy to use when the service receives an alert from New Relic, and select the desired Notification Urgency for incidents (available only with Basic or higher plans). Click Add Service when you are finished.

  3. Copy the Integration Key for your new service:

    API-Integration-Key

In New Relic

  1. Go to Alerts Beta, 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 beta and they’ll need to know about any problem you experience in order to fix them.

FAQ

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.