FireHydrant Status Page Setup
Note: This article is about FireHydrant's built-in status pages. For information about integrating with Atlassian Statuspages, visit this page.
You can create a new Status Page in FireHydrant by clicking Status Pages in the top nav.
Once you create the page by adding a page name and a subdomain that you intend to use for the page, we will generate a CNAME for you. You will then need to configure your chosen subdomain name in your DNS provider.
After we've generated the CNAME record for the page, you will be able to edit some additional details about your page.
Note: We are currently supporting a legacy version of status pages for some customers. If you have previously created a status page, then you can test out new features by opting-in to the new Status Page experience under Page Settings. Some fields listed below are only available as part of the new Status Page experience.
|Name||The name we'll use for your page in the FireHydrant app.|
|Light Mode Logo||A logo to display when a user is viewing the status page in light mode|
|Dark Mode Logo||A logo to display when a user is viewing the page in dark mode.|
|Favicon||Customize the favicon for your status page|
|Open Graph Image||The image that is displayed in social media or link previews when linking the status page on other websites.|
|Page Settings||While we are rolling out our updated status pages, this is a setting toggle on the new features and designs for existing pages. Toggling this on will show some additional form fields|
|Page Title||A title that is displayed when a logo is not present.|
|Welcome Title||A greeting/headline for the page|
|Welcome Message||A message to help your viewers understand the content and goals of the page|
|Operational Message||A message to display when all systems and services are operational.|
|Operational||What conditions to show as "Operational" in the status page. By default, FireHydrant comes with "Operational", "Unavailable", "Degraded", and "Bug" as options. These can be configured and customized in your settings under Incident Response > Severities in the application. Typically, "Operational" is inserted here.|
|Degraded||What conditions to show as "Degraded" in the status page. Typically, "Degraded" is inserted here.|
|Offline||What conditions to show as "Offline" in the status page. Typically, "Unavailable" is inserted here.|
|Components||Which Service Catalog items you'd like to display on the status page. We typically see people show their Functionalities, but you can choose from Environments, Functionalities, or Services to display. You can add components to groups and subgroups to roll-up component conditions. Read more about configuring components groups here|
|Component History||Turn component 90-day on or off for the page.|
|Links||Add up to two custom links to the top of your status page.|
|Fields||Add any additional fields to the incident pages on your status page.|
Managing Components and Component Groups
To add components to your status page, click the "Manage Components" buttons to open the component editor. In the component editor, you can add top-level components or create groups or subgroups of components.
To create a group, click "Add Group." Then you'll be prompted to name your group and add components. Once you added at least one group, you can nest any additional groups underneath another group, creating subgroups. When components are grouped together, they will create a roll-up status and 90-day history of status based on the child components.
After you first create your page, you are presented with a CNAME target to point your domain at our system.
You will want to find and use the documentation for whichever DNS provider you use. But generally you'll need to generate a CNAME record for your domain and point it to the generated CNAME value FireHydrant provides. The example below is from Namecheap, and points the
acme subdomain of this domain to the status page (visit this example page):
To confirm that your DNS is configured correctly, use
dig from the command line or Google's DNS toolbox.
➜ ~ dig +short status.example.com aabbccddeeff.sp-production.firehydrant-customer.com.
After you have correctly configured your DNS record, FireHydrant provisions a TLS certificate and your page will be live.
Note: New DNS records can take anywhere from several minutes to hours to update and propagate depending on the provider.
You can limit the audience of your status page to your employees or other groups of customers. This is an enterprise feature. To enable, visit the appropriate instructions for your SSO provider:
- Learn how to use your new FireHydrant statuspage.