Sentivel has a built-in importer for Atlassian Statuspage and Instatus. It brings across your components (with their grouping), your incident history with the full update threads, and your confirmed email subscribers. You paste an API key, the import runs once, and re-running it is always safe because nothing is ever added twice.
What the importer moves
- Components, with their current status and their group layout mirrored as sections on your Sentivel page.
- Incident history, up to the most recent 500 incidents, including every customer-facing update in each thread.
- Confirmed email subscribers, so your customers keep getting notified without re-subscribing.
Scheduled maintenance windows are not imported automatically, because they are a different object in Sentivel; the importer tells you how many it skipped so you can recreate the upcoming ones. Monitors are also not created for imported components, since Statuspage has no monitoring to import from; you attach Sentivel monitors afterwards.
Step 1: Get your Statuspage API key and page ID
In Statuspage, open your avatar menu and choose API info. Copy the API key and the page ID shown beside it. For Instatus, create a key under Developer settings; the page ID is in the dashboard URL.
Step 2: Run the import
In Sentivel, go to Status pages and choose Import from Statuspage or Instatus. Pick the source, paste the key and page ID, choose which Sentivel page to import into, and press Import. The key is used once for the fetch and never stored. A summary shows exactly what was added and what was skipped.
Step 3: Attach monitors
Imported components show their history but have no checks yet. Add an HTTP, keyword, TCP, or heartbeat monitor for each component you want verified automatically. From then on the component's status is driven by real checks with flap protection, so a single network blip never opens a false incident.
Step 4: Map your third-party dependencies
This is the part Statuspage doesn't do. Map which of your components rely on which providers (AWS, Stripe, Cloudflare, and the rest of the catalog). When a provider you depend on has an incident, Sentivel posts a clear advisory on your page naming the provider, and clears it when the issue resolves.
Step 5: Move your domain
Point your status subdomain's CNAME at Sentivel under the page's custom-domain settings, verify, and your page is live at the same address your customers already know. Keep the Statuspage subscription until you've confirmed the new page, then cancel it.