k6 Cloud to Metabase Integration
AI-first ETL from k6 Cloud into Metabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads k6 Cloud into Metabase
Datrise syncs k6 Cloud's test runs, thresholds, checks, metrics, virtual users, and response times 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
k6 Cloud: Load testing runs and performance thresholds.
Metabase: Open-source analytics with questions, dashboards, and embedded insights.
How k6 Cloud entities map to Metabase
| k6 Cloud entity | Metabase object | Notes |
|---|---|---|
| test runs | k6_cloud_test_runs | id PK · custom fields → flattened columns for the question builder |
| 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 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 k6 Cloud to Metabase sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for k6 Cloud
Early access
Connect k6 Cloud 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.