DatriseAI-first ETL

Statuspage to Metabase Integration

AI-first ETL from Statuspage into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Statuspage into Metabase

Datrise syncs Statuspage's incidents, components, status updates, subscribers, maintenance windows, and uptime metrics into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Statuspage: Public service status and incident history.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Statuspage entities map to Metabase

Statuspage entityMetabase objectNotes
incidentsstatuspage_incidentsid PK · custom fields → flattened columns for the question builder
componentsstatuspage_componentsid PK · linked to statuspage_incidents
status updatesstatuspage_status_updatestemporal columns for trends events
subscribersstatuspage_subscribersid PK · linked to statuspage_incidents

FAQ

How does Datrise handle Statuspage's custom fields in Metabase?

Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.

How does the Statuspage to Metabase sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Statuspage to Metabase the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.