VictorOps to Metabase Integration

How Datrise loads VictorOps into Metabase

Datrise syncs VictorOps's incidents, alerts, on-call schedules, teams, escalation policies, and acknowledgements 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

VictorOps: On-call rotation and incident alerting.

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

How VictorOps entities map to Metabase

VictorOps entity	Metabase object	Notes
incidents	`victorops_incidents`	id PK · custom fields → flattened columns for the question builder
alerts	`victorops_alerts`	id PK · linked to victorops_incidents
on-call schedules	`victorops_on_call_schedules`	id PK · linked to victorops_incidents
teams	`victorops_teams`	id PK · linked to victorops_incidents

FAQ

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

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

Related pipelines

Early access

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