Docs / Data sources / k6 Cloud

k6 Cloud

Business software

Built when you ask for it

Sync k6 Cloud test, test run, metric, and project data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The k6 Cloud connector syncs your load-testing data into analytics-ready tables in your data warehouse. Pull tests, test runs, metrics, and projects from the k6 Cloud API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Tests
  • Test runs
  • Metrics
  • Projects

How it gets built

  1. Choose k6 Cloud when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads k6 Cloud's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against k6 Cloud itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

Bearer token (Personal or Stack API token) + X-Stack-Id header. Generate a Personal or Stack API token in Grafana Cloud and pair it with your Stack ID, found under Testing & Synthetics > Performance > Settings.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a k6 Cloud connector?
Not as a finished connector yet. Ingest builds it from k6 Cloud's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can k6 Cloud data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

k6 Cloud API documentation: https://grafana.com/docs/grafana-cloud/observe-and-act/testing/k6/reference/cloud-rest-api/

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request k6 Cloud