An incident coordinates team members across work channels.
Each incident has a timeline of posts listing comments from users and updates to the state of the incident. Posts can be generated by scripts, service integrations, and direct user submissions.
Creating a new incident is the starting point when you are using Transposit as an incident responder.
Incidents can be created in three different ways.
- Alerts. Automatically via incoming alerts, as described in Alerts and Webhooks in combination with Alert Rules.
- Slack. By an incident responder using Transposit Slack commands, as described in Transposit Slack Commands.
- Transposit. By an incident responder clicking Create Incident in the top right of Transposit to begin creating your incident manually outside Slack.
One or more incident types have been prepared for you by your team's administrator. When an alert is received, the administrator may have defined that an incident should automatically be created.
When you use Slack or when you click Create Incident, one or more incident types are shown, defined by your team's administrator. Pick the incident type applicable to your needs.
Fill out the fields provided by your selected incident type.
Optionally, when you're manually creating an incident in Slack or by clicking Create Incident in Transposit, enable the Quiet mode checkbox to prevent user notifications or on-call pages from being sent. Especially when you're running end-to-end webhook and incident flows during configuration testing, quiet mode is useful because it doesn’t generate any notifications.
Click Create, unless the incident has been created automatically via an alert. Use the timeline to track its progress, while running automations to resolve it.
Watch this quick screencast for an overview of the ways in which incidents can be created in Transposit.
Click here for more videos.