Do you toss and turn at night worrying about the availability of your app? Do you wake up to calls from your boss telling you the site was down all night? Well, then we have great news just for you! We partnered with:
That's right, we're announcing that as of today New Relic and PagerDuty are seamlessly integrated to provide you with even more alerting capabilities. The PagerDuty and New Relic integration extends New Relic's existing alerting feature and allows you to dispatch alerts to your team via phone calls and SMS alerts. You will now be able to trigger, acknowledge, and resolve incidents directly in PagerDuty.
What does this all mean for you? Most importantly, you will be able to respond to and fix problems more quickly, which helps you minimize expensive downtime. It also means that when you turn the lights off at night - you can finally put your mind at ease and catch up on those critical Z's. Just make sure to leave your phone on and keep it on your bedside table. You know, just in case.
How do you get started? First off, you need a New Relic Standard or New Relic Pro subscription. If you don't have one, you can get one here. You will also need a PagerDuty account. If you don't have one one of those, you can get one here. Then, simply authorize the PagerDuty integration by following these steps:
1. Log in to your New Relic Account.
2. Click [Your Company Name] > Account settings > Alert notifications.
3. From the Alert notifications > PagerDuty tab, click the Alert with PagerDuty button.
4. Login to PagerDuty, and authorize New Relic to trigger and resolve alerts in your PagerDuty account.
Optional: To set alerts for downtime event only, select the option from the Alert notifications > PagerDuty tab and then click Save my changes.
Once authorized, you'll be able to select the escalation policy to use for New Relic incidents. The PagerDuty integration is available now and the whole process takes only a couple of minutes to complete!
Happy Paging!
The New Relic Team
The views expressed on this blog are those of the author and do not necessarily reflect the views of New Relic. Any solutions offered by the author are environment-specific and not part of the commercial solutions or support offered by New Relic. Please join us exclusively at the Explorers Hub (discuss.newrelic.com) for questions and support related to this blog post. This blog may contain links to content on third-party sites. By providing such links, New Relic does not adopt, guarantee, approve or endorse the information, views or products available on such sites.
