Posting Incident Updates

Throughout the course of an incident, responders will want to post updates on the status of remediation. On FireHydrant, you can do this by making use of Incident Updates/Notes.

Incident notes are "elevated" updates about an incident that are more prominent and important than chat messages posted into the timeline or incident channel, and often also get propagated outward to status pages.

They also enable usage of the Time since last incident note Runbook conditions, which are useful for e.g. reminding responders to post updates on a cadence or if too much time has gone by without any updates.

Note: If you have configured status templates you will see a dropdown for them in the FireHydrant UI when you select Add an update or when you run the /fh update command in Slack.

Via Command Center

In the Command Center for the incident, navigate to the Status Pages tab.

The internal status page will always be available to post to on incidents. External status pages can optionally be added manually or via Runbook steps.

Click "Add an update" next to the status page you would like to post out to. All of these updates will register on the Incident Timeline as incident notes.

Adding a note to a status page via Command Center
Adding a note to a status page via Command Center

Via Slack

There are multiple commands available for posting updates in Slack:

/fh add note
/fh post
/fh update

When posting an incident note from Slack, you'll also be able to automatically post out to both internal and external status pages.

Adding an incident update with `/fh add note`
Adding an incident update with `/fh add note`

Note: /fh update does not currently work with the Time since last incident note Runbook condition. If you're relying on this condition, we recommend using /fh add note or /fh post.

Last updated on 2/9/2024