Linking Monte Carlo as a source
This source is currently in alpha. The interface and available tables may change.
Connect your Monte Carlo account to pull your data observability history – alerts, monitors, observed tables, users, and warehouse connections – into the PostHog Data Warehouse. This is useful for building data quality scorecards and correlating data incidents with downstream product impact.
Prerequisites
You need a Monte Carlo account with permission to create API keys.
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.
To connect Monte Carlo, you need an API key:
- In your Monte Carlo dashboard, go to Settings → API → Keys and click Create Key.
- Choose a description and an expiration for the key, then create it.
- Copy both the key ID and the key secret. The secret is only shown once.
- Back in PostHog, enter the key ID and key secret, then click Next.
Monte Carlo API keys expire on the date you chose when creating them. When a key expires, syncs stop with an authentication error and you need to create a new key and update the source.
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 alerts table supports incremental syncing on createdTime (new alerts) or updatedTime (new alerts plus status changes on existing ones). The initial sync only pulls the last 365 days of alerts. All other tables are full refresh, as Monte Carlo's API doesn't expose server-side timestamp filters for them.
Configuration
| Option | Type | Required |
|---|---|---|
API key ID | text | Yes |
API key secret | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
alerts | Only syncs the last 365 days on initial sync | Incremental, Full refresh | createdTime, updatedTime | — |
monitors | Monitors configured in Monte Carlo — the table, metric, validation, and custom rule checks that watch data assets and raise alerts. | Full refresh | — | — |
tables | Tables and views Monte Carlo observes across your connected warehouses, with health and activity metadata. | Full refresh | — | — |
users | Users in your Monte Carlo account, useful for attributing alert ownership and monitor authorship. | Full refresh | — | — |
warehouses | Warehouse connections integrated with Monte Carlo (e.g. Snowflake, BigQuery, Redshift). | Full refresh | — | — |
Troubleshooting
If syncs fail with an authentication error, your API key has likely expired or been revoked. Create a new key in Monte Carlo under Settings → API → Keys and update the source credentials in PostHog.
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.