Linking SigNoz as a source
This source is currently in alpha. The interface and available tables may change.
Connect your SigNoz workspace to sync logs, traces, alert rules, dashboards, and notification channels into the PostHog data warehouse. This lets you join observability data with product analytics, for example correlating error logs or slow traces with user behavior.
Prerequisites
- A SigNoz Cloud workspace (e.g.
example.signoz.io) or a self-hosted SigNoz instance reachable over HTTPS. - A SigNoz API key. API keys are created from service accounts, and only users with the Admin role can create service accounts. A key with the Viewer role is enough for syncing.
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.
You'll need your SigNoz host and an API key:
- Your SigNoz host is your SigNoz Cloud tenant hostname (e.g.
example.signoz.io) or your self-hosted instance URL. - To create an API key, in SigNoz go to Settings > Service Accounts, create a service account, then generate a key from its Keys tab.
- Back in PostHog, enter the host and API key, then click Next.
- Select the tables you want to sync, set the sync method and frequency, then click Import.
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.
The logs and traces tables support incremental syncs on their timestamp field and are bounded by your SigNoz retention window on the initial sync. Alert rules, dashboards, and notification channels are small configuration tables that fully refresh on each sync.
Configuration
| Option | Type | Required |
|---|---|---|
SigNoz host | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
logs | Limited to your SigNoz retention window on initial sync | Incremental, Full refresh | timestamp | — |
traces | Limited to your SigNoz retention window on initial sync | Incremental, Full refresh | timestamp | — |
alert_rules | Alert rule definitions configured in SigNoz. | Full refresh | — | — |
dashboards | Dashboard definitions configured in SigNoz. | Full refresh | — | — |
notification_channels | Notification channels alerts can be routed to (Slack, PagerDuty, webhook, etc.). The receiver configuration payload is omitted because it contains credentials. | Full refresh | — | — |
Troubleshooting
- Invalid SigNoz API key: the key was rejected. Generate a new key from a service account in Settings > Service Accounts and reconnect.
- Missing permissions: the service account's role doesn't allow reading this data. Check the role and reconnect.
- Older logs or traces are missing: the initial sync can only reach back as far as your SigNoz retention window.
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.