Connect your status page

Atlassian Statuspage and Instatus now connect under Status pages on the Integrations page, each with an API key. Firefight lists your pages with the key before it saves anything, so a wrong key is refused on the form. See Connect a status page.

What Halon reads. Your pages, components, open and past incidents with every update, maintenance, subscribers and metrics. Name a page or a component by its name, so you can ask Halon to set "Checkout" to a major outage without looking up an id. Every answer links to the page as your customers see it.

What Halon can change. Open an incident and post updates, schedule maintenance, set a component's status, write and publish a postmortem on Statuspage, manage subscribers, and the rest of what each provider's API offers. Every change is seen by your customers, so each one needs a grant, follows your approval rules and asks before it runs in a chat. A tool that would notify subscribers asks whether to tell them, with no default. Halon never changes a status page while it investigates.

Secrets stay in the provider. Settings that work as passwords, such as a monitor's credentials or a page's SMS provider, are never sent or shown, so set those in the provider itself.