Bot commands: Incident management
Getting started
The Blameless Bot allows users to easily orchestrate incidents with less toil and provides a comprehensive framework to speed up incident resolution and data collection.
With the Blameless bot installed, users can start an Incident through Slack by running Blameless “slash” commands from the designated channel or any channel that Blameless Bot has been invited to.
When the user runs/blameless start incident
a modal will pop up asking the user to select an incident type, the severity level, and add a brief description of the incident. Any configurations made for Incident Types and Severity Namings will be populated in the Incident Creation modal as options.
Note: Blameless is limiting the Severity Label display length for Slack. The user can add more than 75 characters, but the Slack Label truncates at 75 characters in the dropdown.
The Blameless Bot has recently undergone some updates recently to improve and clarify the actions involved.
-
Silent Mode's replies are applied as threads to the incident in question.
-
Blameless Bot Compact mode messaging focuses on useful information.
-
Tasks are grouped by assigned user, with required tasks being tagged with an asterisk, and if they have links, they are so displayed as containing a link.
-
The assigned user can now see all of their tasks grouped together at once.
-
The Task list will update as a task is completed or roles are assigned.
Important: Completing non-assigned tasks in Slack fails (as expected), even though selecting “Completed” and the checkmark appears in the associated check box--implying the task has been completed.
Non-assigned tasks cannot be completed before first being assigned to a user/role. Youmustassign a user/role to the task first. After you assign a user/role to a task, you can check the task to complete it. The task description changes to strikethrough in the window, which is the indication that the task is completed.
If you attempt to complete a non-assigned task in the Slack Incident Channel, you will be able to check it, however, it will be followed by an error message appearing at the bottom of the list of tasks.
You may need to scroll down the list of tasks to be able to see this error message and in the Task window, the task remains checked, but the description no longer has the strikethrough.
Note that the task check box will remain checked until you leave the channel and come back into the incident channel (refreshing the channel). If you do so, you will see that the task is actually still incomplete (unchecked).
Note: At any point, if you’re unsure of what the slash command is, typing/blameless
and pressing ENTER, will show the user various options that they can run.
Blameless Bot Commands
Incident Management
Action |
Slash Command |
---|---|
General command to open the UI shell which contains other categorized commands |
|
Starts an incident of a specific severity and type |
|
Permanently deletes this incident |
|
Sets the incident severity |
|
Sets the incident type. Note: Changing the incident type will not affect the tasks created for the incident based on the previous incident type.) |
|
Sets the incident status |
|
Sets the incident description |
|
Sets the status of the incident to Resolved |
|
Shows the incident details |
|
Creates a follow-up action |
|
Shows the latest incidents |
|
Shows tags associated with the incident |
|
Add tags to a category for the incident |
|
Removes tags from a category for the incident |
|
Displays pending and/or completed tasks assigned to you or to anyone |
|
Displays pending and completed tasks assigned for the given incident status. |
|
Marks an incident or swimlane task as completed |
|
Marks an incident task as pending |
|
Creates a new task for the incident or swimlane associated with the channel |
|
Displays key events from the incident timeline |
|
Invites user to the incident channel |
|
Assigns user to the specified incident role |
|
Unmutes bot notifications for the current incident channel |
|
Marks incident as a duplicate of another incident |
|
View the "on call" engineer for a specific PagerDuty service |
|
Retrospectives
Action |
Slash Command |
---|---|
Assign a user to a retrospective role |
|
Sends retrospective as an email.Note:Multiple email addresses can be specified by using spaces as the separator |
|
Swimlanes
Action |
Slash Command |
---|---|
Creates a swimlane for the incident |
|
Close the swimlane |
|
Edit the working theory for a swimlane |
|
Update the owner of the swimlane |
|
Reopen a previously closed incident swimlane |
|
Shows the swimlanes for the incident |
|
Shows details for the selected swimlane |
|
Comments
0 comments
Article is closed for comments.