Linking Sonar Cloud as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
The Sonar Cloud connector syncs projects, issues, metrics, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your SonarQube Cloud user token and organization key to sync code-quality data.
Generate a user token under My Account → Security in SonarQube Cloud, and find your organization key on your organization's homepage.
You'll be asked for:
- User token
- Organization key: for example
my-organization. - Region: choose between EU (sonarcloud.io) and US (sonarqube.us).
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Sonar Cloud tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
User token | password | Yes |
Organization key | text | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | Projects (top-level components) in the organization, as returned by components/search_projects. | Full refresh | — | — |
issues | Code issues (bugs, vulnerabilities, code smells) across the organization's projects. | Full refresh | — | — |
metrics | Definitions of the metrics SonarQube Cloud can compute (coverage, bugs, duplications, ...). | Full refresh | — | — |
quality_gates | Quality gates defined in the organization (the pass/fail conditions applied to analyses). | Full refresh | — | — |
rules | Coding rules available to the organization, which resolve the rule keys on issues. | Full refresh | — | — |
quality_profiles | Quality profiles of the organization: the set of rules active for one language, from qualityprofiles/search. | Full refresh | — | — |
measures | Current metric values per component (project, directory, or file), one row per component and metric, from measures/component_tree. | Full refresh | — | — |
measures_history | Metric values per project over time, one row per project, metric, and analysis, from measures/search_history. | Full refresh | — | — |
issue_changelog | Change history of each issue (status, assignee, severity, and other field changes), from issues/changelog. | Full refresh | — | — |
components | Component inventory of each project: its directories, files, and test files, from components/tree. | Full refresh | — | — |
project_quality_profiles | The quality profile each project uses for each language, including the default profiles, from qualityprofiles/search with a project filter. | Full refresh | — | — |
pull_requests | Analyzed pull requests of each project, with their quality gate status and issue counts, from project_pull_requests/list. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the user token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.