Creating resolved incidents
When an incident doesn't require active incident management, you can create a Resolved Incident. Resolved incidents start at the "Resolved" milestone and skip any automatic runbooks that you have configured. Users will also be required to add a start and end time to the incident to populate the appropriate milestones.
Note: Resolved incidents allow users to manually add runbooks, so you can use Incident Types to ensure that Resolved Incidents use the appropriate runbooks for non-active incidents. Learn more about incident types here.
From any screen in the FireHydrant web application, open the menu to the right of the "Declare Incident" button and select "Create Resolved Incident".
In the Create Resolved Incident form, you will be required to add a name, a start date and time, an end date and time, and any other required fields. Additionally, you can select an incident type or add any additional details by selecting additional fields at the bottom of the form. By either using Incident Types that have a runbook selected or by manually selecting a runbook, you can add any automation that you would like to run to a resolved incident.
Once the details are completed, click "Create Incident" to create the incident and view the resolved incident page.
In a Slack workspace with the FireHydrant bot installed, run
/fh create-resolved to begin creating a resolved incident.
In Slack, users will be required to enter a start date and time as well as an end date and time. The rest of the form will follow the logic of your form settings from your Slack integration with FireHydrant, including required fields, visible fields, and where applicable, field sort order.
Just as in the web interface, you can explicitly add a runbook to this incident for any automation you may need. Where applicable, incident types can also be used to add runbooks to these incidents by selecting a runbook when defining the incident type.
You can create a resolved incident via the API by using the
milestone field in the Create Incident endpoint. Including a milestone with
type: "resolved" will skip any automatic runbook triggers.
// A sample body sent to the endpoint
name: "A sample incident"