FireHydrant Status Pages Overview

Note: This article is about FireHydrant's built-in status pages system-wide and per-incident. For information about Atlassian Statuspages, visit this page instead.

Keeping users informed during incidents is critical. When you experience an incident, customers want to know what steps you're taking to resolve it.

FireHydrant Status Pages enable you to communicate with customers, both internal and external, about ongoing incidents. You can use Status Pages to update customers using the same tools and workflow that you already use to manage incidents.

FireHydrant offers two status page types:

  1. Incident-specific (e.g. "internal") status pages
  2. System-wide (e.g. "external") status pages

Incident-specific status pages

Also called Internal status pages, each incident automatically creates its own page where high-level information about the incident is shown.This makes it easy to share high-level incident information with internal stakeholders or any other team members who have the page URL without requiring them to log in.

To read more about them, visit Internal Status Pages.

System-wide status pages

System-wide status pages are available all of the time and show an overarching view of your entire system and which components are currently impacted by incidents.

To read more about system-wide status pages, check out FireHydrant Status Page Setup and Using FireHydrant Status Pages.

Last updated on 9/15/2023