PagerDuty

The PagerDuty snap-in integrates DevRev's incident management with the PagerDuty platform. Synchronize the DevRev incident object with PagerDuty incidents using the PagerDuty incident subtype. Create, update, and escalate incidents seamlessly between the two.

For more information, refer to the PagerDuty snap-in on the DevRev marketplace.

Installation

1. In DevRev, go to Settings > Snap-ins and click Explore Marketplace in the top-right corner.
2. In the DevRev marketplace, find PagerDuty and click Install.
3. Set-up the snap-in's configurations.
4. Click Save > Install snap-in.
5. Execute the /pagerduty register-webhook command in the snap-in Discussions tab. Upon successful start, you will see the message Successfully registered DevRev webhook..

Configuration

In Configure, the following configuration options are available:

• PagerDuty API Token: Set up the PagerDuty API connection: create or select your Snap-in Service connection with a PagerDuty API Access Key. Ensure that the API Access Key has a Full access level.

  If the configured API key has a Read-only access level, the PagerDuty snap-in will not be able to make changes on your PagerDuty instance. The DevRev webhook will also have to be manually set up on PagerDuty Generic Webhooks - v3. Make sure to select the desired scope and event subscriptions.

• PagerDuty Services Rev Part: Select the DevRev rev part that all your PagerDuty services serve when first created as DevRev runnables.

  • The snap-in creates and maps your PagerDuty services as runnable dev parts in DevRev. DevRev dev parts always serve (are linked to) a specific rev part.
  • After snap-in installation, you can update each runnable dev part to serve a different rev part.

• Update PagerDuty Incident Priority: Toggle whether the DevRev incident severity field should synchronize with the PagerDuty incident priority field.

  If toggled on, the PagerDuty priority name mapping for each DevRev severity value 0-4 must be provided.

• Synchronize Incident Discussions and Notes: Toggle whether the DevRev incident discussions should synchronize with the PagerDuty incident notes.

• Update PagerDuty Incident Name: Toggle whether PagerDuty incident titles should be updated with the respective DevRev incident's ID.

  The format is: [INC-XXX] - Original Incident Title.

• Default PagerDuty Service Runnable Part: Optionally specify the default runnable part to be used when no impacted part is selected on incident creation.

  Select a runnable part that is mapped to a PagerDuty service.

• Default PagerDuty Escalation Policy ID: Optionally specify the default selected escalation policy when delegating through the /delegate command.

  Enter the PagerDuty escalation policy ID.

Removal

1. Execute the /pagerduty unregister-webhook command in the snap-in Discussions tab. Upon successful removal, you will see the message Successfully unregistered DevRev webhook.
2. Remove or Deactivate the snap-in.