Posting Updates

Responders typically post updates on the remediation status throughout an incident. Incident updates are more formal updates about the remediation status and are often posted to status pages. FireHydrant supports this via Incident Updates/Notes.

Note that you can only post to status pages if they have been added or attached to the incident. This can be done manually or automatically via Runbooks. For more information, see External Status Pages.

All updates will always be posted to the incident's Internal Status Page.

Via Slack

With linked external status pages, you can post any incident notes directly from Slack. Multiple commands are available for posting updates in Slack (all open the same modal).

/fh update
/fh add note # alias
/fh post     # alias

Via Command Center

In the Command Center for the incident, you can click the additional primary action dropdown on the right side to reveal the "Update incident" action. This opens a modal that functions the same way as the Slack modal above.

Alternatively, you can navigate to the Status Pages tab to post to individual status pages. The internal status page will always be available to post updates. External status pages can optionally be posted to, but if you post to an external page, FireHydrant will also automatically post to the Internal status page.

Status Templates

If you have Status Templates configured, your responders can select from a list of pre-defined update templates to further reduce cognitive load and toil during incidents. This dropdown will not be visible if no status templates exist. You can visit the docs linked above for more information.

Additional Notes

• Runbook Conditions - Posting incident updates will trigger the condition Time since last incident note if it is used in any of your Runbooks or steps. This allows you to do things like reminding the channel to post an update if it's been 30 minutes since the previous update, etc.

Next Steps

• Look into configuring Status Templates
• Read about Triggering Runbooks, the automation engine on FireHydrant
• Learn how to mark Impacted Components on incidents