Skip to main content

​
PagerDuty and Wirespeed integration benefits

  • Create PagerDuty incidents automatically when Wirespeed cases are escalated
  • Route incidents to the PagerDuty service selected during setup
  • Map Wirespeed case severity to high- or low-urgency PagerDuty incidents
  • Resolve PagerDuty incidents when their associated Wirespeed cases are closed
  • Synchronize acknowledgements, resolutions, and notes between PagerDuty incidents and Wirespeed cases

​
How it works

  • When a Wirespeed case is escalated, Wirespeed creates an incident on the configured PagerDuty service. The incident includes the Wirespeed case details and uses the configured case incident title template when one is provided.
  • Wirespeed maps critical and high-severity cases to high-urgency incidents. Other severities create low-urgency incidents.
  • When a Wirespeed case is closed, Wirespeed resolves the associated PagerDuty incident. If the case is closed with notes, Wirespeed adds the close note to the incident.
  • When a detection is added to an escalated Wirespeed case, Wirespeed adds a note to the associated PagerDuty incident.
  • Wirespeed creates a webhook subscription for the selected PagerDuty service. Through this webhook, resolving an incident closes the associated Wirespeed case, acknowledging an incident marks the case as responded to, and annotating an incident adds a note to the case.

​
Requirements

  • An active Wirespeed account with permission to add and configure integrations
  • An active PagerDuty account and a PagerDuty user who can access the service used for Wirespeed incidents
  • Permission to manage incidents and webhook subscriptions for the selected PagerDuty service
Wirespeed uses PagerDuty classic OAuth and requests the write scope. PagerDuty’s classic OAuth write scope includes read and write access. Wirespeed requires write access to create and update incidents and manage webhook subscriptions. It requires read access to list available services and existing webhook subscriptions. The integration does not require you to create or enter an API key. PagerDuty issues an OAuth access token after authorization, and Wirespeed stores the token encrypted in its integration credential storage. The connection is tied to the PagerDuty user who authorizes it, so Wirespeed can only access services and perform actions that user is permitted to access.

​
Support

If you need help with this integration, use the Chat button in Wirespeed to contact our engineers or email support@wirespeed.co.

​
Integration walkthrough

​
In PagerDuty

You do not need to create a PagerDuty service integration or copy an integration key. Before starting, confirm that the PagerDuty service you want to use already exists and that your PagerDuty user can manage incidents and webhook subscriptions for it. PagerDuty prompts you to authorize Wirespeed through OAuth during setup.

​
In Wirespeed

  1. Sign in to Wirespeed and navigate to Integrations > Add Integration
  2. Select PagerDuty, then click Integrate
  3. In the PagerDuty authorization tab, review the requested write OAuth scope and click Accept to authorize Wirespeed as your PagerDuty user
  4. Return to Wirespeed and refresh the Integrations page
  5. Select the newly added PagerDuty integration
  6. Select the PagerDuty Service where Wirespeed should create incidents
  7. Optionally, enter a Case Incident Title Template to customize incident titles
  8. Click Save
When you save the configuration, Wirespeed creates a webhook subscription for the selected service and subscribes to incident.resolved, incident.acknowledged, and incident.annotated events.

​
How to uninstall

  1. Sign in to Wirespeed and navigate to Integrations
  2. Select the connected PagerDuty integration
  3. Click Delete
  4. Enter the requested confirmation text, then confirm the deletion
Deleting the integration stops synchronization between Wirespeed and PagerDuty and removes the webhook subscription created by Wirespeed. Existing PagerDuty incidents and Wirespeed cases are not deleted.