Linking Cronitor as a source

Alpha release

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

The Cronitor connector syncs your monitors, their recent job invocations, and time-series reliability metrics into the PostHog Data Warehouse, so you can analyze scheduled-job reliability, run durations, and failure trends alongside your product data.

Prerequisites

You need a Cronitor account and an API key with the monitor:read scope. Cronitor creates default API keys for every account, and you can create additional scoped keys at any time.

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

API key – find or create one under Settings → API keys in your Cronitor account. The key needs the monitor:read scope.

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 monitors and invocations tables have no server-side time filter in the Cronitor API, so they always sync as a full refresh. The invocations table is a snapshot of each monitor's most recent runs; for long-term trends, use the metrics table, which syncs incrementally over time windows using its stamp field.

Configuration

Option	Type	Required
`API key`	password	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`monitors`	A Cronitor monitor: a cron job, heartbeat, or uptime check, with its configuration and current read-only state.	Full refresh	—	—
`invocations`	Recent invocations (runs) of each job monitor, from the monitor detail's latest_invocations. A snapshot of recent history, refreshed each sync.	Full refresh	—	—
`metrics`	Time-series reliability metrics per monitor, from the Metrics API. One row per monitor, dimension, and timestamp.	Incremental, Full refresh	stamp	—

Troubleshooting

If you see an authentication error, your API key is invalid or has been revoked. Create a new key in your Cronitor account's API settings, then reconnect.
If you see a permissions error, the key is missing the monitor:read scope. Update the key's scopes, then reconnect.

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.