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.
You'll need to have Owner privileges on FireHydrant and also be logged into your Atlassian Statuspage account.
- Sign in to Statuspage.
- Click your avatar in the lower left and select API Info.
- Click Create Key and enter a name (we suggest “FireHydrant”).
- Copy the key that it provides for the next section.
- Sign in to FireHydrant as an Owner.
- On the current navigation, click into Integrations in the left nav.
- On the new navigation, click into Settings on the top nav followed by Integrations on the left side.
- Click the '+' next to Statuspage.
- Paste the API key from step 4 into the API token field and click Authorize Application.
Select the Statuspage that you want to link to FireHydrant.
Once you've selected the right Statuspage, Severity Map and Condition Map sections will appear below.
- These sections are where you will map FireHydrant severities and conditions to Statuspage severities and conditions.
Save these settings to finalize the integration's setup.
Note: For our Atlassian Statuspage integration, each Status page is its own connection - if you need to connect multiple, see the next section.
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.
Once the integration is set up, you'll now want to either import or link a Statuspage component to a FireHydrant Functionality. This step is required for automatically marking the right components impacted when publishing to Statuspage from FireHydrant.
- On the old user interface, click on Service catalog > Functionalities on the left-hand nav.
- In the new user interface, click on Catalog at the top nav followed by Functionalities on the left.
- On the right, click on Add functionality > Import from third party and then select StatusPage from the list of third-party sources.
- On the next page, you can import all components or choose which ones to import/link. Both buttons will take you to the same next screen, but Import all components will automatically check all the components.
Here, you can now check/uncheck which components you'd like to import or link, and then in the dropdown, you can choose to either:
- Create New which will create a new Functionality with the same name as said component and auto-link both
- Link to existing which will create a link between the Statuspage component and the existing Functionality in FireHydrant.
When you're done choosing, click Import selected pages. You can confirm whether this worked by going to the Functionalities in question from the confirmation page and checking underneath the External Links section of a Functionality.
Note: At this time FireHydrant only supports linking Atlassian Statuspage components to FireHydrant Functionalities, not Services or Environments.
Once you've performed the above steps, you'll have options to create an incident on and post updates to each Statuspage you've configured.
The Runbook step allows you to automatically create a Statuspage incident, templatize the messaging, and mark the linked component impacted when you create an incident on FireHydrant.
For more information, view the docs here.
Alternatively, you can manually create a Statuspage incident via an incident's Command Center, seen below, by clicking "+ Add" next to pages under the Inactive section.
As you transition through your incident milestones on FireHydrant, we'll also update the public status, too. For example, if you set Mitigated on an incident in FireHydrant, we'll post a Monitoring update on Atlassian Statuspage depending on how you mapped your conditions. When you resolve an incident, naturally, we'll resolve it on Statuspage too.
Note: This does require the Statuspage to have been attached to the incident in the first place. See the previous subsection on creating Statuspage incidents.
As you work through the incident, you can also add public notes. Within the Command Center, you can directly go to the Status Pages tab and add an update, which you will find under the Active pages subsection.
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 or