Statuspage
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Connect Statuspage to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Sync your Atlassian Statuspage data. Create a key under Manage account > API info and paste it below. The key has organization-wide management access; no extra scopes are required.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Linking Statuspage to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Statuspage
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
pages | Status pages in your Statuspage organization. | Full refresh | — | — |
components | Individual services or features whose status is shown on a status page. | Full refresh | — | — |
component_groups | Groups that bundle related components together on a status page. | Full refresh | — | — |
incidents | Incidents and scheduled maintenances published to a status page. | Full refresh | — | — |
incident_templates | Reusable templates for drafting incidents. | Full refresh | — | — |
subscribers | People and endpoints subscribed to status updates for a page. | Full refresh | — | — |
metrics | System metrics displayed on a status page (e.g. response time, uptime). | Full refresh | — | — |
metric_providers | External providers (Datadog, New Relic, Pingdom, etc.) supplying metric data. | Full refresh | — | — |
page_access_users | Users granted access to view a private/audience-specific status page. | Full refresh | — | — |
page_access_groups | Groups of users granted access to a private/audience-specific status page. | Full refresh | — | — |