DatriseAI-first ETL

Pagerduty to Metabase Integration

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

How Datrise loads Pagerduty into Metabase

Datrise syncs Pagerduty's incidents, services, schedules, escalation policies, log entries, and responders 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

Pagerduty: Incident response, on-call schedules, and escalation.

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

How Pagerduty entities map to Metabase

Pagerduty entityMetabase objectNotes
incidentspagerduty_incidentsid PK · custom fields → flattened columns for the question builder
servicespagerduty_servicesid PK · linked to pagerduty_incidents
schedulespagerduty_schedulesid PK · linked to pagerduty_incidents
escalation policiespagerduty_escalation_policiesid PK · linked to pagerduty_incidents

FAQ

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

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

Related pipelines

Early access

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