Linking Logz.io 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 Logz.io connector syncs search logs, alerts, triggered alerts, 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 Logz.io API token to sync your log data, alerts, and account configuration. Create a token under Settings → Tools → Manage tokens → API tokens in your Logz.io account, and pick the region that matches your account.
Log search is bounded by your account's retention window.
You'll be asked for:
- API token
- Region: choose between US East (api.logz.io), EU (api-eu.logz.io), UK (api-uk.logz.io), Canada (api-ca.logz.io), Australia (api-au.logz.io) and West US 2 (api-wa.logz.io).
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 Logz.io tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
search_logs | Individual log documents returned by the Logz.io search API, one row per Elasticsearch document. Bounded by the account's log retention window. | Incremental, Full refresh | @timestamp | — |
alerts | Alert definitions configured in the account. | Full refresh | — | — |
triggered_alerts | History of alert firings — one row per triggered alert event. | Full refresh | — | — |
notification_endpoints | Notification endpoints (Slack, PagerDuty, webhooks, etc.) available to route alerts to. | Full refresh | — | — |
drop_filters | Drop filters configured to discard matching logs before indexing. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API 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.