Publishing to External Status Pages

One of the primary components of incident response is managing communications externally to end users or other impacted parties. Often, organizations will use status pages for these updates.

The FireHydrant platform offers both internal status pages, which are meant for the internal team only and require no setup, as well as external status pages (Atlassian and FireHydrant-hosted), primarily used to communicate to external end-users or scoped audiences.

Attaching Status Pages to Incidents

Attaching status pages to FireHydrant incidents allows creating incidents on said pages and seamlessly posting incident updates.

Prerequisites

In order to publish incidents and post updates to these status pages, you will need to first set up the integrations. Visit the documentation links for the supported provider(s) below:

• Atlassian Statuspage
• FireHydrant-Hosted Status Pages

Automatically via Runbook

Runbook steps will automatically create incidents on the configured status pages as well as link the status pages to the incident when executed.

Depending on which provider you're using, you can make use of different Runbook steps. See the documentation for:

• Atlassian Statuspage
• FireHydrant Status Page

Manually via Command Center

From the Command Center of an existing incident, click on the Status pages tab. Below, you should see a list of your configured status pages (both FireHydrant and/or Atlassian Statuspage) under the Inactive section. Click '+ Add' next to the page you'd like to attach to the incident, and it will attach to the incident and show up under the Actve section.

Next Steps

Now that you've seen how to attach status pages to incidents, see how you can seamlessly post updates to them as you work your way through an incident.