Configure Statuspage Mappings and Templates

Before you start

• Save a Statuspage API key in the integration first.
• Decide which pages this workspace is allowed to publish to.

Do this

1. In Settings > Integrations > Statuspage, save the API key and load the available pages.
2. Add each Statuspage page the workspace should use and mark any default pages.
3. Link Statuspage components to the matching systems or functions in the catalog.
4. Review severity-to-impact mapping so sev1 through sev4 produce the public impact you want.
5. Review incident-status mapping so OpsBell states map cleanly to Statuspage incident states.
6. Review component-status mapping so components move to the right health state as the incident progresses.
7. Set the public title and message templates using incident tokens.
8. Test with one controlled incident and confirm the public output before you rely on it.

Check it worked

• The workspace can discover Statuspage pages and components.
• Incidents publish to the right page and linked components.
• Public title and message output look correct without manual cleanup.

If it does not work

• If pages do not load, rotate or recheck the API key first.
• If components are not updating, confirm the system or function linkage.
• If the public message is wrong, adjust the template before changing the incident workflow itself.

Next

• Publish to Statuspage
• Create systems and functions