Create/Update an incident on your Atlassian Statuspage

FireHydrant integrates with Atlassian Statuspage and can automatically create incidents as part of your incident response process.

Prerequisites

First, you'll want to make sure you've set up and configured your Atlassian Statuspage(s).
When setting up Statuspage(s), it's important that you either import the components or link the components to FireHydrant Functionalities afterwards. Only with the links can FireHydrant properly mark the appropriate components as impacted on your Atlassian Statuspage.

Creating a Statuspage incident

Once you've configured the integration(s), add the Create a Statuspage.io incident step to a Runbook.

On the Details tab, add a title for the step.
On the Conditions & scheduling tab, create rules that dictate at what point during the incident response process the status page should be published.

A typical setup is shown below: when an incident is created, we will automatically copy over the incident name as the Statuspage incident's title, and the description on the incident as the Statuspage incident's message.

You can parameterize and choose what pieces of information you want to include - see the full list of Liquid variables here.

Creating a Statuspage incident via Runbook step

When this Runbook step executes, Atlassian Statuspage is updated with an incident and your custom message. For example:

Creating a new incident with these parameters...

...results in this output on your Statuspage

Updating a Statuspage incident

If a FireHydrant incident is sync'd with a Statuspage incident, you can continue to make updates to the Statuspage incident throughout the incident lifecycle both from the user interface and from Slack (with /fh update or /fh post).

Posting updates to Statuspages from Command Center

The above would result in:

Example update propagated from Slack to Statuspage