Linking IBM Instana Observability 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.

The IBM Instana Observability connector syncs your events (incidents, issues, and changes), application and service catalogs, monitoring configuration, and infrastructure inventory into the PostHog Data Warehouse, so you can track reliability trends alongside your product data.
Prerequisites
You need an Instana account (SaaS or self-hosted) with permission to create an API token. The token's permission scopes control which tables can be synced, so grant read access for the data you want to import.
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.
When linking Instana, you'll need:
- Base URL – the address you use to open the Instana UI, e.g.
https://unit-tenant.instana.io, or your self-hosted domain. - API token – create one under Settings → Team Settings → API Tokens in Instana.
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 events table supports incremental sync using the event start timestamp (epoch milliseconds) and only reaches back 30 days on the initial sync, matching Instana's event retention. The other tables are configuration and topology catalogs without an updated-since filter, so they sync as full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
Base URL | text | Yes |
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
events | Only syncs the last 30 days on initial sync | Incremental, Full refresh | start | — |
applications | Application perspectives defined in Instana's application monitoring. | Full refresh | — | — |
services | Services discovered by Instana's application monitoring. | Full refresh |





