Linking Airbrake as a source
This source is currently in alpha. The interface and available tables may change.
The Airbrake connector syncs your error monitoring data – projects, error groups, error occurrences (notices), and deploys – into PostHog, so you can track error rates by project and environment over time and correlate error spikes with deploys.
Prerequisites
You need an Airbrake account with a user API key. Every project your user can access is synced.
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 need your Airbrake user API key. Find it in your Airbrake User settings (your profile menu in the Airbrake dashboard). Per-project keys in Airbrake only allow error submission and won't work for syncing data.
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 groups table supports incremental sync on createdAt, which only picks up newly created error groups. Fields that change on existing groups (like noticeCount, resolved, and lastNoticeAt) are only refreshed by a full refresh, so consider scheduling periodic full refreshes if you rely on those fields.
The notices table fetches occurrences per error group across every project, making it the most API-expensive table. It is not synced by default and only the most recent pages of history are pulled per group.
Configuration
| Option | Type | Required |
|---|---|---|
User API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | Airbrake projects accessible to the connected user key, with per-project error and deploy counters. | Full refresh | — | — |
groups | Incremental syncs only pick up newly created error groups; fields that mutate on existing groups (noticeCount, resolved, lastNoticeAt) are only refreshed by a full refresh | Incremental, Full refresh | createdAt | — |
deploys | Deploys tracked per project. Airbrake's API returns no deploy identifier, so this table is full-refresh only; projectId is added by PostHog for joinability. | Full refresh | — | — |
notices | Individual error occurrences, fetched per error group across every project — the most API-expensive table, capped at the most recent pages per group | Full refresh | — | — |
Deploy rows don't include a project reference in Airbrake's API, so PostHog adds a projectId column to the deploys table for joining against projects.
Troubleshooting
If the source fails to connect or a sync stops with an authorization error, your user API key is likely invalid or revoked – generate a new key in your Airbrake user settings and update the source credentials.
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.