Create a separate chat channel for every incident to keep things tidy. No more combing through threads and direct messages.
Use schedules to understand who is responsible for triaging incidents, and automatically invite them to incident channels.
Automatically track the hours spent fixing data pipeline issues, so you can understand the true impact of breakages.
Create incidents and escalate automatically when something breaks.
Keep track of next steps by exporting follow-ups to the responsible team’s issue tracker.
When an alert is triggered, escalate it to the owners of the impacted service.
Matilda from our data team spoke all about data incidents at this years Coalesce conference. If you're looking for practical, tool-agnostic approaches to for resolving, communicating, and learning from data incidents, it's well worth a watch.