Linking Scalr as a source

The Scalr connector syncs your Terraform and OpenTofu infrastructure data – environments, workspaces, and runs – into PostHog, so you can analyze infrastructure-as-code activity alongside your product data.

Note: This source is in alpha. If you run into issues, please let us know.

Prerequisites

You need a Scalr account with API access. Create a service account token in Scalr with read access to environments, workspaces, and runs.

To create a token, go to Account scope > IAM > Service accounts in Scalr and generate a new token with the required permissions.

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 Scalr, you'll need:

• Scalr hostname – the public hostname of your Scalr account (e.g., example.scalr.io).

• Account ID – your Scalr account ID (e.g., acc-example). Find this in your Scalr account settings.

• API token – a service account token with read access to environments, workspaces, and runs.

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.

The workspaces table supports incremental sync using the updated_at field. The environments and runs tables use full refresh only.

Runs use full refresh because their status changes over time and the Scalr API doesn't expose an update filter for this resource.

Configuration

Supported tables

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.