Create PagerDuty Incidents from GitLab issues
Create PagerDuty Incidents from GitLab issues
Problem to solve
Responders need to be automatically notified when an alert is triggered. PagerDuty is one of the most common on-call and paging tools in market and is used by many of our enterprise customers. We want to enable the creation of PagerDuty incidents from GitLab issues via the PagerDuty Incident Creation API.
Intended users
Further details
This work contributes to the Incident Management Vision
Proposal
Enable creation of PagerDuty Incidents from a specific GitLab issue. This could be achieved via a quick action that sends a GitLab issue to PagerDuty and creates an incident
Design
We are designing for the following workflow:
- User creates an incident issue
- They realize they need to page someone to address the incident
- They utilize a slash command on the incident issue to create a PD incident (and thus page the appropriate people).
To allow this to happen, we're imagining we'll need a space to configure a PagerDuty integration and to create an appropriate Slack command.
Configuration
As part of #119018 (closed), we're adding a tab for PagerDuty integrations. The plan is to add some additional introductory text and an additional field to this section to enable users to create PagerDuty incidents from GitLab issues. The required updates are highlighted in the following mock-up:
Slack command
The proposal is that users can create a PagerDuty incident by utilizing the slash command /pagerduty. Assuming the configuration has been correctly completed, typing in this command will automatically create a PagerDuty incident.
We'll also need to ensure that, when the slack command is created, it's added to the prompt screen that appears as users type:
Permissions and Security
Documentation
Documentation Required. Please add a new section here.
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.