Integrations / SonarQube

SonarQube

SonarQube code quality and security platform for projects, issues, quality gates, measures, and engineering risk signals.

Bearer token

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A SonarQube server or SonarCloud org Telara can reach.

A user who can generate a user token (or a global analysis token, matching what the form asks).

Vendor setup

Get the credential

Open My Account → Security

In SonarQube or SonarCloud, click your avatar → My Account → Security.

Generate a token

Under Generate Tokens, name it for Telara, pick User Token, click Generate. Copy it once.

Paste in Telara

Settings → Integrations → SonarQube. Enter the host without scheme (SonarCloud is sonarcloud.io) and paste the token.

In Telara

Connect in Telara

Bearer token

SonarQube user token or service token. Store base_url as the SonarQube/SonarCloud host without scheme.

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for

Base Url
API token

Knowledge

What gets indexed

Resource	Coverage
Projects	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Projects	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Projects.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Project tokens cannot list other projects. Use a user token whose permissions cover what Telara should see.

On-prem SonarQube must be reachable from Telara.