PageDuty gives DevOps and IT Ops Teams Full-Stack Visibility and Actionable Insights for Better Software and Better Customer Experiences
Does your team love Slack? Are they big fans of PagerDuty? So are we! That's why we built an awesome Integration to help you get the most out of PagerDuty from within Slack. RigD gives you complete control over your PagerDuty incidents so you can quickly route, remediate, and resolve them. When the going gets tough RigD makes it easy to assemble the team and collaboratively troubleshoot an incident. And we'll keep an eye out for patterns in your troubleshooting to help resolve future incidents even faster.

Pass the Pager to RigD

Connecting PagerDuty to RigD is super simple. You’ll need your Pager Duty API Key, if you need help finding that here is a link to the PagerDuty docs Generate a PagerDuty API Key. Now just ask RigD to add rigd tool. Then choose PagerDuty and click on the button that appears. The dialog helps ensure no sensitive info is posted to the channel history. Give your tool integration a name and description, and add the pagerduty token. RigD always limits tool access to the creator, so if you want others to be able to work with PagerDuty incidents in Slack you will want to change the scope to Controlled or Entire Workspace. Just hit add and your good to go!

Get the PagerDuty Slack App Now!

Now Cut through the Noise

With three simple actions you will have your incidents feeding into just the right place in Slack.

  1. Use create pagerduty feed to add a PagerDuty Service to RigD
  2. Use attach pagerduty feed to deliver incident messages from a feed to a channel
  3. Use filter pagerduty feed to include or exclude incident messages from the channel based on a query

Once you add a feed to RigD, incident messages will also automatically be routed to the assigned users when RigD can match the the PagerDuty user to a Slack user.
When you need to call on the team for help with an incident, RigD can open a group chat and capture the troubleshooting and resolution. This substantially drives down Mean Time to Identification and Resolution. Just tell RigD you want to work pagerduty incident. When your done RigD will process the data to aid future troubleshooting. You can edit or view these digests: try get pagerduty digest.

PagerDuty Capabilities

PagerDuty Capabilities

  • Feed incidents to a channel
  • Filter incoming incident events and send to different channels
  • Route incident messages directly to assignees in Slack
  • List open incidents and get incident details
  • Acknowledge, assign, escalate, resolve, note, or merge incidents
  • Work an incident in a group channel and capture all the troubleshooting and remediation activity
  • Get a digest of all the troubleshooting activity and refine it to improve future troubleshooting
  • Fix an ncident in slack and automate resolutions for future incidents
  • Update incident title
  • Send a message to incident team
  • Who’s on call
  • Add responders
  • Auto add responders and assigned to working channel
  • Run a response play
  • Update digest time to identification to time to acknowledge
  • Add incident details to digest for summary, service, assigned to, responders, urgency, priority
})(jQuery)