Connect PagerDuty

InfraNest monitors your websites, APIs, servers, domains and certificates. Connect PagerDuty and the right person is paged the moment one of them needs attention, and the incident closes itself when the problem is fixed.

#PagerDuty + InfraNest Integration Benefits

• Page the person on call when something breaks. A monitor that goes down pages at critical. A domain, certificate or server that needs attention pages too, one incident per problem.
• Close incidents automatically. When the problem recovers, InfraNest resolves the PagerDuty incident.
• Work in either tool. Acknowledge, resolve or add a note in PagerDuty or in InfraNest, and the other one follows, with the person's name.
• See what changed before it broke. Deploys, DNS changes and server actions show under Recent changes in PagerDuty, next to the incident. They never page anyone.
• See who is on call on your monitors and incidents in InfraNest, without opening PagerDuty.
• Route with your own data. Every page carries the monitor's name, tags, impact and your custom fields, ready for PagerDuty Event Orchestration.

#How it Works

• When a monitor goes down, InfraNest triggers an incident on the PagerDuty service you chose. Repeat alerts for the same problem update that one incident instead of opening new ones.
• When several monitors on one server go down together, they share one PagerDuty incident, so on-call is paged once per outage.
• When a domain, certificate or server needs attention, InfraNest triggers an incident for it. A domain that becomes free to register is sent at warning, which PagerDuty treats as low urgency by default.
• When the problem recovers, InfraNest resolves the PagerDuty incident.
• When someone acknowledges, resolves or adds a note in PagerDuty, the InfraNest incident shows it. The same works the other way around.
• InfraNest creates one Events API v2 integration named InfraNest on each service you choose, and one webhook for your account. It never changes your escalation policies, schedules, users, teams or other integrations.

#Requirements

• An InfraNest Owner or Admin.
• For one-click connect: a PagerDuty Admin or Account Owner installs InfraNest on your PagerDuty account once. After that, anyone who can add integrations to a service can connect.
• A PagerDuty account in the United States (app.pagerduty.com) or the European Union (eu.pagerduty.com).
• Integration-key setup works on any PagerDuty plan and needs no PagerDuty admin.

#Support

If you need help with this integration, please contact InfraNest support at support@infranest.io, or open a ticket from Help in the InfraNest app. For security questions, write to security@infranest.io.

#Integration Walkthrough

There are two ways to connect:

• One click (recommended). InfraNest sets up PagerDuty for you, and acknowledgements, notes and on-call names work right away.
• Integration key. You create the integration in PagerDuty yourself and paste its key into InfraNest.

#In PagerDuty

Install InfraNest on your account (one click, once per account)

Skip this if someone has already installed InfraNest on your PagerDuty account.

1. In InfraNest, go to Integrations and select PagerDuty.
2. Under What connecting PagerDuty does, find the line that starts with Before the first sign-in. Type your PagerDuty subdomain into the address: acme for acme.pagerduty.com, or acme.eu for an EU account.
3. Open that address, or send it to a PagerDuty Admin or the Account Owner.
4. In PagerDuty, review the permissions InfraNest asks for and approve the install. It takes a minute and needs no InfraNest account.

Integrating With a PagerDuty Service (integration key only)

1. Go to Services and select Service Directory.
2. Select the service you want InfraNest to page, or create a new one.
3. On the service's Integrations tab, select Add an integration.
4. Choose Events API V2 and select Add.
5. Expand the new integration and copy its Integration Key (32 characters).

#In InfraNest

Connect with one click

1. Go to Integrations and select PagerDuty.
2. Set PagerDuty service region to Europe if your account is at eu.pagerduty.com. Otherwise, leave it on United States.
3. Select Connect PagerDuty. In the PagerDuty window, sign in if asked and select Authorize.
4. Back in InfraNest, choose the service to page.
5. Review what InfraNest will set up, then select Finish setup.

If a step needs a PagerDuty role you don't have (usually the webhook, which needs an Admin), InfraNest tells you before you finish, sets up everything else, and gives you a link to send to an admin for that one step.

To page another service later, select Add a service on the account.

Connect with an integration key

1. Go to Integrations, select PagerDuty and open Prefer to set it up yourself?.
2. Choose the PagerDuty service region, paste the Integration key, and select Connect.
3. On the new account, select Send monitor alerts here.

To get acknowledgements and notes back from PagerDuty as well, follow If you connected with an integration key.

Check that it works

1. On the account, select Send test incident.
2. InfraNest triggers a real incident on the service (on-call may be notified) and resolves it right away.
3. InfraNest shows whether PagerDuty accepted the incident and whether PagerDuty reported back.

When everything is set up, the account shows Ready for Outbound alerts, Inbound updates, Automation triggers and Automation actions.

#How to Uninstall

1. In InfraNest, go to Integrations → PagerDuty, open the ⋯ menu on the account and select Disconnect.

2. Review the list. It names everything InfraNest removes from PagerDuty: its integrations, its webhook, and maintenance windows that haven't started yet. Automations that use the account are switched off, not deleted.

3. Select Disconnect.

4. If you connected with one click, remove InfraNest's access in PagerDuty too. PagerDuty doesn't let apps remove their own access. The person who connected goes to Integrations → OAuth Apps → InfraNest and selects Revoke Your User Token. A PagerDuty Admin can select Uninstall there instead, for the whole account.

5. If you connected with an integration key, delete the Events API V2 integration from the service's Integrations tab in PagerDuty, and your webhook under Integrations → Generic Webhooks (v3) if you made one.

Past incidents keep their link to the PagerDuty incident, marked Disconnected.

If PagerDuty no longer accepts the account's sign-in (for example, the person who connected it has left), InfraNest can't remove anything in PagerDuty. Select Remove from InfraNest anyway, then delete the webhook under Integrations → Generic Webhooks (v3) and the InfraNest integration on each service's Integrations tab yourself.