- Teams like engineering, communications, legal…
- Different impacts across products, services or regions with different groups working on mitigations
- Groups exploring independent approaches towards resolution, or investigations on root causes
Creating a stream
To create a stream, simply type/incident stream in an incident channel.
You’ll be presented with a modal to:
- Set a name for the stream
- Assign someone as the stream lead - this will usually be a different person to the main incident lead to avoid splitting their focus
- Invite anyone else who should collaborate on the stream
If you’ve configured automatic call links we’ll also create one for your stream. If not, you can also manually link a video call from the stream channel, just like in an incident channel .
Updating a stream
To create an update, simply type/incident update in a stream channel, just like you would in an incident channel.
You’ll be presented with a modal that:
- Allows you to provide a short message to update people with what’s going on (’ Can you share any more details ’)
- Lets you set a reminder for your next update: no need to remind yourself manually! We will come back and remind you when an update is due.
Closing a stream
Once a stream of work is complete, type/incident close in the stream channel.
You’ll be presented with a modal that asks you to provide a final update on the stream.
The stream will be marked as as closed, and the final update will be posted in the incident channel to keep everyone up to speed.
Roles in streams
Just like incidents, you should nominate a person to lead each stream. We recommend you have a separate lead for each stream to the incident, as they cover different areas of work in different Slack channels. If you have set up custom incident roles , we’ll also make those available in streams. Any role available in the parent will be available in its streams. From within the stream channel you can use commands such as/inc lead and /inc handover just as you would in an incident to reassign the roles in that stream.
Streams in your incident timeline
Activity that occurred in a stream will be included in your incident timeline in both the dashboard, and your exported postmortem. We’ll highlight which stream each item occurred in.
Restricting access to streams
This can be done by making a private stream from a public incident. Read more about that here .Streams shortcuts cheatsheet
If you’ve learnt just one command you can use it in streams too!/inc while in a stream’s Slack channel will pop up a menu of all the actions you can run in a stream.
Emojis
From an stream’s Slack channel, you can react to messages with:Slack Commands
| Command | Description | |
|---|---|---|
| ROLES | ||
/incident lead | Make someone the stream lead `/incident lead [me | @user]` to auto-fill the lead |
/incident roles /incident role | View, assign and unassign roles in the stream | |
/inc handover | Hand over responsibilities in a stream to another user. | |
| COMMUNICATION | ||
/incident update | Provide an internal status update to your team about the stream | |
/incident close | Provide a closing update, and mark the stream as closed | |
/incident request /incident request-update | Request an internal status update from the stream lead | |
/incident escalate /incident page | Pull in other teammates for help | |
/incident call | Set a call link /incident call [link] to auto-fill the link | |
/incident statuspage | Post or update an incident on your status page |