An incident management framework centralized around a ChatOps bot to allow your teams to easily and effectively identify and manage technical incidents impacting your cloud infrastructure, your products, or your customers' ability to use your applications and services.
NOTICE: As of February 2nd, 2025, the Helm charts repository has moved from https://charts.incidentbot.io to https://docs.incidentbot.io/charts - please update your usage accordingly.
- Organize your efforts into Slack channels to coordinate incident response
- Easy to read messages that get to the point without a ton of visual distractions
- Completely customizable status, severity, and role definitions to control all stages of incident response
- Communicate with the bot using ephemeral messages to keep clutter out of your channels
- Keep the rest of your organization informed with an incident digest channel that explains the state of all incidents
- Integrate with tools you already use like Confluence, Jira, Opsgenie, Statuspage, PagerDuty, and Zoom
- Automatically build a postmortem document base to save time
- A web interface for advanced features and organizational capabilities [TBD]
Interested in a web interface to use with Incident Bot? Check out the console project here.
- Create a Slack app for this application. You can name it whatever you'd like.
- Select
from an app manifestand copymanifest.yamlout of this repository and paste it in to automatically configure the app and its required settings. Be sure to override any customizable settings like name, etc. - You'll need the app token, bot token, and user token for your application and provide those as the
SLACK_APP_TOKEN,SLACK_BOT_TOKEN, andSLACK_USER_TOKENenvironment variables - these can be found within the app's configuration page in Slack. For more information on Slack tokens, see the documentation here. - You'll need a Postgres instance to connect to. If trying the bot out using Docker Compose or Helm, there are options to run a database alongside the app.
- Configure and deploy the application using one of the methods described in the documentation, or however you choose. (There's a Docker image available.)
Full setup documentation is available here.
Please see contribution guidelines before opening a pull request.
This application is not meant to solve every problem with regard to incident management. It was created as an open-source alternative to paid solutions.
If you encounter issues with functionality or wish to see new features, please open an issue or a feature request to let us know.