Linking Rollbar as a source

Alpha release

This source is currently in alpha. The interface and available tables may change.

The Rollbar connector syncs your error tracking data into PostHog, so you can analyze errors alongside your product data.

Prerequisites

You need a Rollbar project and a project access token with the read scope. Each PostHog source connects to one Rollbar project, so add one source per project.

Adding a data source

  1. In PostHog, go to the Sources tab of the data pipeline section.
  2. Click + New source and click Link next to this source.
  3. Enter your credentials (see Configuration below) and click Next.
  4. 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 Rollbar, you'll need:

  • Project access token – find or create one in your Rollbar project under Settings → Project Access Tokens. A token with the read scope is sufficient.

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_at timestamp). 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.

Configuration

OptionTypeRequired
Project access tokenpasswordYes

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
items

An error item grouping together occurrences of the same error in a project.

Full refresh
occurrences

A single occurrence (instance) of an error item, with full event details.

Incremental, Full refreshid
deploys

A deployment recorded in Rollbar, marking a release of code to an environment.

Full refresh
environments

An environment configured in the Rollbar project (e.g. production, staging).

Full refresh

Troubleshooting

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.

Community questions

Was this page useful?

Questions about this page? or post a community question.