k6 Cloud to Holistics Integration

How Datrise loads k6 Cloud into Holistics

Datrise syncs k6 Cloud's test runs, thresholds, checks, metrics, virtual users, and response times into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

k6 Cloud: Load testing runs and performance thresholds.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How k6 Cloud entities map to Holistics

k6 Cloud entity	Holistics object	Notes
test runs	`k6_cloud_test_runs`	id PK · custom fields → flattened columns for the modeling layer
thresholds	`k6_cloud_thresholds`	id PK · linked to k6_cloud_test_runs
checks	`k6_cloud_checks`	id PK · linked to k6_cloud_test_runs
metrics	`k6_cloud_metrics`	id PK · linked to k6_cloud_test_runs

FAQ

How does Datrise handle k6 Cloud's custom fields in Holistics?

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

How does the k6 Cloud to Holistics sync stay up to date?

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

Related pipelines

Early access

Connect k6 Cloud to Holistics 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.