DatriseAI-first ETL

Opsgenie to ClickHouse Integration

AI-first ETL from Opsgenie into ClickHouse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Opsgenie into ClickHouse

Datrise syncs Opsgenie's alerts, incidents, schedules, escalations, teams, and notification logs into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

Opsgenie: On-call alerting and incident escalation.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Opsgenie entities map to ClickHouse

Opsgenie entityClickHouse objectNotes
alertsopsgenie_alertsid PK · custom fields → JSON or Map columns
incidentsopsgenie_incidentsid PK · linked to opsgenie_alerts
schedulesopsgenie_schedulesid PK · linked to opsgenie_alerts
escalationsopsgenie_escalationsid PK · linked to opsgenie_alerts

FAQ

How does Datrise handle Opsgenie's custom fields in ClickHouse?

Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.

How does the Opsgenie to ClickHouse sync stay up to date?

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

Connect Opsgenie to ClickHouse 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.