RigD Delivers Deeper PagerDuty Integration to Improve Incident Lifecycle Management

PagerDuty Establishes RigD as Verified Partner

 

RigD for PagerDuty lets you automate many important PagerDuty activities right through Slack. Our Slack bot for PagerDuty saves Ops teams a lot of time.

 

We’ve been working closely with PagerDuty and I’m happy to share that PagerDuty recognizes the value we bring to customers and has added RigD as a Verified Partner.  We use the latest PagerDuty APIs and we are excited to be able to quickly add features that provide the value needed for Digital Operations.

 

 

 

 

 

 

 

 

 

 

Here are four major benefits RigD gives PagerDuty users:

  • RigD helps drive efficiency into the workflow from the identification point on…
  • RigD accelerates data collection for incident diagnosing issues by providing the mechanisms to gather the data right from within Slack.
  • RigD brings incident data and the relevant people into Slack to facilitate faster root cause identification.
  • RigD captures and learns from all of the troubleshooting interactions to help teams develop automation to drive faster MTTR for future issues.

 

Our new release

Being an agile SaaS service we are always adding features, but at some point we have enough new capabilities to declare a major milestone.  We are also pleased to announce that we recently released deeper PagerDuty integration in our RigD workbot.  Building upon our conversations with PagerDuty customers at Summit, we added many new activities that round out augmenting work in the incident lifecycle.   Adding activities around technical setup, assess, respond and learn make DevOps, IT Operations, Support Engineering, Incident Coordinators and Incident Commanders much more efficient in their work buy giving them increased control over the PagerDuty operations all within Slack where the teams are collaborating to acknowledge, identify and remediate the business impacting issues.

 

With the new release, we have the following capabilities, broken out by the PagerDuty Incident Lifecycle

 

Technical Setup

 

RigD core:

Add RigD Tool: Adds a new tool to RigD.

Set RigD Tool: Sets a configured RigD tool as the active tool for the specified access scope [user, channel, team].

List RigD Tools: Provides a list of the tools configured.

Get RigD Tool: Gets the details for a configured tool.

Update RigD Tool: Update the tool details.

Update Tool Access: Adds or removes users or channels to tools that are configured for controlled access.

Delete RigD Tool: Deletes a configured RigD tool from the system.

 

PagerDuty Specific:

List PagerDuty Services: Lists all pager duty services.

Create PagerDuty Feed: Creates a webhook based feed for a PagerDuty service and sends it to RigD

List PagerDuty Feeds: lists feeds from PagerDuty Services

Get PagerDuty Feed: gets the details for the feed.

Delete PagerDuty Feed: Deletes the specified feed.

 

Assess

 

Attach PagerDuty Feed to Channel: Attach a PagerDuty service feed to this Slack channel.

Create PagerDuty Feed Filter: creates a filter for a PagerDuty feed in the channel

List PagerDuty Filters: Lists the filters for the specified feed for this channel.

Delete PagerDuty Feed Filter: Deletes the filter for the specified feed in this channel.

List PagerDuty Incidents: Lists the open incidents for a service or user with optional urgency filter. Each entry includes a link back to the incident in PagerDuty

Detach PagerDuty Feed From Channel: Removes the specified feed from the channel

 

Respond

 

Incident Related

Get PagerDuty Incident: gets the details for an incident.

Acknowledge PagerDuty Incident: acknowledges the incident and optionally adds a note.

Update PagerDuty Incident Title: Update the title of an incident

Resolve PagerDuty Incident: resolves the specified incident and optionally adds a note

Update PagerDuty Incident Status: Updates the status for the specified incident. Use Slack snippits for notes if RigD is getting confused.

Snooze PagerDuty Incident: Snoozes an acknowledged incident for a specified number of minutes.

Escalate PageDuty Incident: escalates an incident to the specified escalation level

Get PagerDuty Incident Alert: Gets the details of the specified incident alert

Merge PD Incidents: Merges one or more incidents into a single one.

Assign PagerDuty Incident: assign the incident to the specified user and optionally add a note

Add PagerDuty Incident Note: Adds a note to the specified incident. Use Slack snippits for notes if RigD is getting confused.

 

Responder and Response Plays

Add PagerDuty Responders: Adds one or more responder requests to an incident.

List PagerDuty Response Plays: Get a list of response plays

Run PagerDuty Response Play: Runs a response play for a specified incident.

 

On Call

Get PagerDuty On Call: Gets the current on call users for each escalation level for the given service or teams schedules.

 

Work an Incident in Slack

Work PagerDuty Incident: Create a group message with collaborators for the specified incident, and add a note with link to discussion.

 

Learn

 

Get PagerDuty Incident Digest: Retrieves a digest of the troubleshooting session for PagerDuty Incident that was worked through RigD.

 

 

Edit PagerDuty Incident Digest: Remove unnecessary messages and actions from the worked pager duty incidents.

 

RigD offers a free trial, all you need to do is signup for a trial, install the Slack App and have your PagerDuty credentials at hand.

See the RigD workbot live and sign up for a demo.

3 Comments

  • Keith

    Posted at 3:48 pm, November 13, 2018

    Gents, please let me know if Rigd can help me CREATE a pagerduty incident with a specific team, e.g., “rigd new pagerduty incident TeamX” that would then kick off the pager process for the oncall for TeamX

  • Keith Dixon

    Posted at 3:50 pm, November 13, 2018

    Gents — can rigd help me kick off a pd incident, e.g., “rigd new pagerduty incident TeamX” that would then kick off the oncall paging sked for TeamX?

  • Justin Griffin

    Posted at 7:14 pm, November 13, 2018

    Thanks for the suggestion, the team is working on it.

Post a Comment

Comment

Name
Email
Website