Skip to content
Book a demoStart free
Connectors

Grafana Cloud k6 connector

Set up the Grafana Cloud k6 connector in Kaivo: authentication, configuration, the 3 BigQuery tables it syncs, and answers to common questions.

Grafana Cloud k6 connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Grafana Cloud k6 data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your data from Grafana Cloud k6 instead of moving it.

Sync your Grafana Cloud k6 load testing data into BigQuery with Kaivo to analyse performance test results over time.

CategoryTech
AuthenticationAPI key
SetupSelf-service

Getting started with the Grafana Cloud k6 connector

Section titled “Getting started with the Grafana Cloud k6 connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Grafana Cloud k6 account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your API Token.

Field Description
API Token
API token for k6 Cloud. To generate one, follow the k6 Cloud documentation. The token is case sensitive.

|

Tables and columns synced from Grafana Cloud k6

Section titled “Tables and columns synced from Grafana Cloud k6”

Kaivo syncs 3 tables from Grafana Cloud k6 into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

k6-tests (10 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
created STRING Date and time when the k6 test was created.
id INT64 Unique identifier for the k6 test.
last_test_run_id STRING Identifier for the last test run associated with this k6 test.
name STRING Name of the k6 test.
project_id INT64 Identifier for the project to which this k6 test belongs.
script STRING The script content of the k6 test.
updated STRING Date and time when the k6 test was last updated.
user_id INT64 Identifier of the user who owns this k6 test.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
organizations (14 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
billing_address STRING The billing address of the organization.
billing_country STRING The country associated with the billing address of the organization.
billing_email STRING The billing email address for the organization.
created STRING The timestamp when the organization was created.
description STRING A textual description or details about the organization.
id INT64 The unique identifier for the organization.
is_default BOOL Indicates if the organization is set as the default organization.
is_saml_org BOOL Flag showing if the organization uses SAML for authentication.
name STRING The name of the organization.
owner_id INT64 The user ID of the owner or creator of the organization.
updated STRING The timestamp when the organization data was last updated.
vat_number STRING Value-added tax (VAT) number for the organization.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
projects (9 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
created STRING The timestamp when the project was created
description STRING A short description of the project
id INT64 The unique identifier for the project
is_default BOOL A flag indicating if the project is the default one
name STRING The name of the project
organization_id INT64 The unique identifier of the organization the project belongs to
updated STRING The timestamp when the project was last updated
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Grafana Cloud k6 supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Grafana Cloud k6?

Section titled “How long does the initial sync take for Grafana Cloud k6?”

It depends on how much history is in your Grafana Cloud k6 account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Grafana Cloud k6’s schema changes?

Section titled “What happens when Grafana Cloud k6’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Grafana Cloud k6, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Grafana Cloud k6 instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Grafana Cloud k6 connector in Kaivo and all of its synced data is deleted with it.

Common use cases for Grafana Cloud k6 data

Section titled “Common use cases for Grafana Cloud k6 data”

Use k6-tests to track load test results and catch regressions over time.

Join projects with k6-tests to compare performance across services.

Use test results to confirm your systems handle expected load.

Use Grafana Cloud k6 data in your AI and BI tools

Section titled “Use Grafana Cloud k6 data in your AI and BI tools”

Once Grafana Cloud k6 data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Grafana Cloud k6 data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Grafana Cloud k6 connector pricing and plan details.

  • Adform: Sync Adform to BigQuery.
  • Amplitude: Sync Amplitude to BigQuery.
  • Auth0: Sync Auth0 to BigQuery.
  • Convex: Sync Convex to BigQuery.
  • GitHub: Sync GitHub to BigQuery.
  • GitLab: Sync GitLab to BigQuery.