Linking Aiven as a source
This source is currently in alpha. The interface and available tables may change.
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.
Contents
The Aiven connector syncs your projects, services, and billing data from Aiven into the PostHog data warehouse.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Aiven.
- You need an API token from Aiven. Go to your Aiven profile authentication page and create a personal token. If you want to sync billing tables (billing groups, invoices, invoice lines) or organization membership tables, your token needs organization-level read access.
- Back in PostHog, enter the token in the
API tokenfield and click Next. - Select the tables you want to sync, set the sync frequency, then click Import.
Once the syncs are complete, you can start using Aiven data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
projects | Aiven projects — the container that groups services and their billing | Full refresh |
organizations | Aiven organizations — the top-level tenant that owns projects and billing | Full refresh |
services | Running Aiven managed services (Kafka, PostgreSQL, ClickHouse, OpenSearch, etc.) | Full refresh |
billing_groups | Billing groups that aggregate charges for one or more projects | Full refresh |
invoices | Issued invoices for a billing group | Full refresh |
invoice_lines | Per-service cost breakdown on invoices, used for BI cost export | Full refresh |
organization_users | Members of an Aiven organization | Full refresh |
user_groups | User groups within an organization for grouping members and permissions | Full refresh |
clouds | Global catalogue of Aiven cloud regions across AWS, GCP, and Azure (off by default) | Full refresh |
Full refresh tables reload all data on each sync.
Sync limitations
All tables use full refresh only. The Aiven API does not support pagination or server-side timestamp filters, so incremental syncing is not available.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | An Aiven project — the container that groups services and their billing. | Full refresh | — | — |
organizations | An Aiven organization — the top-level tenant that owns projects and billing. | Full refresh | — | — |
services | A running Aiven managed service (Kafka, PostgreSQL, ClickHouse, OpenSearch, etc.). | Full refresh | — | — |
project_users | A member of an Aiven project and the access they hold on it. | Full refresh | — | — |
project_events | An entry in a project's audit and state-change event log. | Full refresh | — | — |
billing_groups | A billing group that aggregates charges for one or more projects. | Full refresh | — | — |
invoices | An issued invoice for a billing group. | Full refresh | — | — |
organization_users | A member of an Aiven organization. | Full refresh | — | — |
user_groups | A user group within an organization for grouping members and permissions. | Full refresh | — | — |
user_group_members | Membership rows linking users to an organization's user groups. | Full refresh | — | — |
billing_group_projects | Mapping of projects to the billing group they are billed under. | Full refresh | — | — |
invoice_lines | A single cost line on an invoice — the per-service breakdown used for BI cost export. | Full refresh | — | — |
clouds | Global catalogue of Aiven cloud regions across AWS, GCP and Azure. | Full refresh | — | — |