Integrating Atlassian Statuspage with FireHydrant

Atlassian Statuspage is a tool for publicizing incidents that are currently occurring with your product. We use them, as well as thousands of other companies. It makes sense to integrate your public status page updates into an incident response process, so we built our Atlassian Statuspage integration to do just that. This guide goes over how to setup and use the integration.

 

Setup

You'll need to be logged in as an owner on FireHydrant and also be logged into your Atlassian Statuspage account.

1. Sign in to Statuspage
2. Click your avatar in the lower left and select ​​API Info
   
3. Click Create Key and enter a name (we suggest “FireHydrant”)
4. Save the key that it provides for the next step
5. Sign in to FireHydrant as an Owner
6. Click into Integrations in the left nav
7. Click the + next to Statuspage
   
8. Paste the API key from step 4 into the API token field and click Authorize Application
   
9. Select the Statuspages that you want to link to FireHydrant and the Functionalities they correspond to, if any.
   
   This step is important if you want to display which components are currently broken to visitors on your Statuspage URL. FireHydrant uses these links to properly add and update components on your Atlassian Statuspage. 
   
   If you want to create functionalities inside of FireHydrant, leave the default "Create New" option selected. Otherwise, you may want to link to previously existing functionalities inside of FireHydrant.
   
   Click Start Import once complete.
   

Next, we need to configure the default page

FireHydrant needs to know which status page we will create updates on, to do this:

1. Head back to the Integrations page and click the Pencil Icon.
2. On this page, you'll see a dropdown to select which page in which FireHydrant will send incident information to. Select the page you'd like to post to.

You'll also see the option to map severities to the impact on Atlassian Statuspage. FireHydrant allows its users to customize the severities in its system, and Statuspage has a more finite set of impacts, so you may want to customize how your severities map to impact displayed to customers publicly.

Save your settings to enable the full power of the integration. You won't be able to create Atlassian Statuspage incidents from FireHydrant unless a default page is selected at a minimum.

Configuring Multiple Statuspages

Each Statuspage tile in the integrations page represents a single connection, and each connection supports one Statuspage as a target. To configure more Statuspages, simply repeat the steps above, and then select a different Statuspage as the target in the dropdown.

Incidents

Once you've performed the above steps, you'll have an option to create a Statuspage incident from FireHydrant's Command Center, seen below, or automatically via a runbook step.

Functionalities

If you linked Statuspage components to FireHydrant functionalities, we'll automatically add those to the incident when you add them to your incident (and have the runbook step configured).

And here it is added to the public incident status.

Milestones

As you transition through your incident milestones on FireHydrant, we'll also update the public status, too. For example, if you set "Mitigated" on FireHydrant, we'll post a "Monitoring" update on Atlassian Statuspage. When you resolve an incident, naturally, we'll resolve it on Statuspage too.

Public Updates

As you work through the incident, you can add public notes as well! Within the Command Center, you can directly go to the Status Pages tab and add an update.

Or, within Slack, you can directly specify if you'd like a note or update to be internal-only or if you want the note propagated externally to your Status Page when you run `/fh update`.

 

That's it! If you have any questions, always feel free to email us at [e-mail]