DatriseAI-first ETL

Instatus to Metabase Integration

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

How Datrise loads Instatus into Metabase

Datrise syncs Instatus's incidents, components, incident updates, subscribers, status page views, and uptime history 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

Instatus: Fast status pages with incident timelines and subscribers.

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

How Instatus entities map to Metabase

Instatus entityMetabase objectNotes
incidentsinstatus_incidentsid PK · custom fields → flattened columns for the question builder
componentsinstatus_componentsid PK · linked to instatus_incidents
incident updatesinstatus_incident_updatesid PK · linked to instatus_incidents
subscribersinstatus_subscribersid PK · linked to instatus_incidents

FAQ

How does Datrise handle Instatus'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 Instatus to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Instatus 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.