Linking Sonatype (Nexus Repository) 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.

Learn more

Alpha release

This source is currently in alpha. The interface and available tables may change.

The Sonatype (Nexus Repository) connector syncs repositories, components, assets, 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.

Connect your Sonatype Nexus Repository instance to pull your artifact inventory.

Enter your instance URL (e.g. https://nexus.example.com) and the username and password of a user with read access to the repositories you want to sync. A user token also works: use the token name code as the username and the pass code as the password.

The tasks table additionally requires the nx-tasks-read privilege; deselect it if your user doesn't have it.

You'll be asked for:

Instance URL: for example https://nexus.example.com.
Username
Password

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_at timestamp). 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 Sonatype (Nexus Repository) tables are full refresh. Each sync replaces the contents of the table.

Configuration

Option	Type	Required
`Instance URL`	text	Yes
`Username`	text	Yes
`Password`	password	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`repositories`	A repository configured on the Nexus instance — hosted, proxy, or group — for a package format such as Maven, npm, Docker, or PyPI.	Full refresh	—	name
`components`	A versioned package (e.g. a Maven artifact, npm package, or Docker image) stored in a hosted or proxy repository. Group repositories are excluded to avoid double-counting their members' components.	Full refresh	—	repository, id
`assets`	An individual file stored in a hosted or proxy repository, such as a .jar, .tgz, or Docker layer, with its checksums, size, and download metadata. Group repositories are excluded to avoid double-counting their members' assets.	Full refresh	—	repository, id
`tasks`	A scheduled or manually triggered maintenance task on the Nexus instance, such as blob store compaction or repository cleanup, with its schedule and last run state.	Full refresh	—	id

Troubleshooting

If the connection fails with an authorization error, the password 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.