SonarQube Cloud connector

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

Written By Lauri Raivio

Last updated 16 days ago

Kaivo is a fully managed data platform that syncs your SonarQube Cloud 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 SonarQube Cloud instead of moving it.

What is the SonarQube Cloud connector

Sync your SonarQube Cloud data into BigQuery with Kaivo to analyse code quality and issues across your projects.

Category	Tech
Authentication	API key
Setup	Self-service

Getting started with the SonarQube Cloud connector

Sign up for Kaivo and create a workspace.
Connect your SonarQube Cloud account.
Choose which tables to sync.
Wait for the initial sync to finish.
Query your data in BigQuery or your favourite AI or BI tool.

Authenticating SonarQube Cloud

Authenticate with your User Token.

Field	Description
User Token	Your User Token. See here. The token is case sensitive.

Configuring the SonarQube Cloud connector

When you set up the connector, you provide:

Field	Description
Component Keys	Comma-separated list of component keys.
Organization	Organization key. See here.
Start Date	To retrieve issues created after the given date (inclusive).

Tables and columns synced from SonarQube Cloud

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

components (7 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`key`	`STRING`	Unique identifier for the component
`name`	`STRING`	Name of the component
`organization`	`STRING`	Name of the organization to which the component belongs
`project`	`STRING`	Name of the project to which the component is associated
`qualifier`	`STRING`	Type of the component (e.g., 'TRK' for a project)
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

issues (19 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`type`	`STRING`	The type or category of the issue
`author`	`STRING`	The author or creator of the issue
`component`	`STRING`	The project component associated with the issue
`creation_date`	`STRING`	The date and time when the issue was created
`debt`	`STRING`	The debt value associated with resolving the issue
`effort`	`STRING`	The estimated effort required to resolve the issue
`hash`	`STRING`	The unique hash identifier of the issue
`key`	`STRING`	The unique key or identifier of the issue
`line`	`INT64`	The line number in the source code where the issue occurs
`message`	`STRING`	The message or description of the issue
`organization`	`STRING`	The organization to which the project belongs
`project`	`STRING`	The name of the project where the issue exists
`resolution`	`STRING`	The resolution status of the issue
`rule`	`STRING`	The rule identifier associated with the issue
`severity`	`STRING`	The severity level of the issue
`status`	`STRING`	The current status of the issue
`update_date`	`STRING`	The date and time when the issue was last updated
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: issues__flows

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.

Subtable: issues__tags

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.

metrics (11 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`type`	`STRING`	The type or format of the metric data (e.g., 'integer', 'float', 'string')
`description`	`STRING`	A brief summary or explanation of the metric data
`direction`	`FLOAT64`	The direction of the metric data (e.g., 'higher is better' or 'lower is better')
`domain`	`STRING`	The domain or category to which the metric data belongs
`hidden`	`BOOL`	Indicates if the metric data is hidden from normal view (e.g., for internal use)
`id`	`STRING`	The unique identifier for the metric data
`key`	`STRING`	The key associated with the metric data (e.g., 'code_quality')
`name`	`STRING`	The name or title of the metric data
`qualitative`	`BOOL`	Indicates if the metric data is qualitative in nature (e.g., 'yes' or 'no')
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the SonarQube Cloud sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where SonarQube Cloud 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.

Frequently asked questions

How long does the initial sync take for SonarQube Cloud?

It depends on how much history is in your SonarQube Cloud 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.

Can I sync only some tables or columns?

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 SonarQube Cloud'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 SonarQube Cloud, 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.

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 SonarQube Cloud 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 SonarQube Cloud connector in Kaivo and all of its synced data is deleted with it.

Common use cases for SonarQube Cloud data

Code quality trends

Use metrics to track quality and coverage across components over time.

Issue analysis

Join issues with components to find where technical debt builds up.

Project view

Use components to compare code quality across repositories.

Use SonarQube Cloud data in your AI and BI tools

Once SonarQube Cloud 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 SonarQube Cloud data.

Claude

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

Power BI

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

Data Studio

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

Tableau

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

Google Sheets

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

Excel

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

Metabase

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

See our pricing page for SonarQube Cloud 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.

Was this helpful?

Still need help? Share an idea