Create Incident
Learn how to quickly create an incident with Flarekit
Last updated
Learn how to quickly create an incident with Flarekit
Last updated
Creating an incident with Flarekit is easy. Once you create the incident, a dedicated Slack channel will be set up in the flr-###-incident-name format and a new thread for the incident will be opened on the #incidents channel.
Run /flarekit in any Slack channel to start creating an incident. You can also add the incident name after this command to pre-populate the field Incident Name in the Create Incident form. For example: /flarekit Google Meet is refusing connection.
When you use this command, a Create Incident form will pop up on the screen.
You can choose an Incident Type among the following options:
Customer Facing: This type of incident affects your customers directly. It means the problem is visible to users and impacts their ability to use your service or product.
Internal System: It involves problems with the systems your team uses to manage and support your service.
Cloud: This type of incident involves issues with cloud services that your application relies on. It could be problems with cloud storage, hosting, or any cloud-based infrastructure.
Deployment Pipeline: This type of incident affects the process of deploying new code or updates to your application. It involves issues in the build, test, or deployment stages.
Defining how serious is the incident you are creating is also very important. In Incident Severity, you can classify the incident as:
Minor: It has a low impact and usually affects a small number of users or a non-critical part of your system.
Major: It has a higher impact and affects a larger number of users or an important part of your system.
Critical: A critical incident severely affects most or all users and crucial parts of your system, requiring an urgent and coordinated response to resolve.
In Incident Lead, you can choose an incident lead from your Slack team as an optional command. This person should start organizing the tasks and guiding people to resolve the issue.
As an optional field, you can also select the Incident Impact to describe how it affects your product's users. The impact options are:
Full Outage: The entire system or service is completely unavailable to all users.
Partial Outage: Only part of the system is down so that some users might be affected.
Non-Production Outage: The issue affects testing or development systems, not the users' main system.
Degraded Performance: The system is running, but it is slower than usual, or some features are not working well.
Security: There is a security issue that could put the system or user data at risk.
Finally, in the Summary field, you can write additional details for your incident. Giving more details about your incident helps everyone stay informed about the issue.
