Linking Bigeye 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.
This source is currently in alpha. The interface and available tables may change.
The Bigeye connector syncs workspaces, sources, tables, 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 a Bigeye API key to pull your data observability metadata.
Generate a Personal or Agent API key from Advanced Settings in your Bigeye workspace. The key inherits your Bigeye role's access (view, edit, or manage).
You'll be asked for:
- API key
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 Bigeye tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
API keyType: password Required: True | |
Bigeye hostType: text Required: False | Leave blank unless your organization uses a self-hosted or regional Bigeye instance. |
Workspace IDType: number Required: False | Only needed if your Bigeye account has more than one workspace. Find it in workspace settings. |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Workspaces | A Bigeye workspace: an isolated collection of connected data sources, tables, and metrics. | Full refresh | — | — |
Sources | A data source (database or warehouse) connected to Bigeye for monitoring. | Full refresh | — | — |
Tables | A table or view discovered by Bigeye within a connected source. | Full refresh | — | — |
Metrics | A configured data quality metric (a check Bigeye runs on a column or table). | Full refresh | — | — |
Collections | A named group of metrics, used to organize monitoring and route alert notifications. | Full refresh | — | — |
Issues | An open or resolved data quality issue, created when one of a collection's metrics alerts. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key 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.