k6 Cloud to PlanetScale Integration

How Datrise loads k6 Cloud into PlanetScale

Datrise syncs k6 Cloud's test runs, thresholds, checks, metrics, virtual users, and response times into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

k6 Cloud: Load testing runs and performance thresholds.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How k6 Cloud entities map to PlanetScale

k6 Cloud entity	PlanetScale object	Notes
test runs	`k6_cloud_test_runs`	id PK · custom fields → JSON columns
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 PlanetScale?

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

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

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

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