Linking StatusCake as a source
This source is currently in alpha. The interface and available tables may change.
The StatusCake connector syncs your uptime, SSL, pagespeed, and heartbeat monitoring data into PostHog – including raw check results, up/down periods, and alerts – so you can compute availability SLAs and track performance regressions alongside your product data.
Prerequisites
You need a StatusCake account with an API token. Tokens are generated under Account Settings > API Keys in the StatusCake dashboard and grant account-wide read access.
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 StatusCake, you'll need:
- API token – generated under Account Settings > API Keys in your StatusCake dashboard. No extra scopes are required.
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 per-test history tables (uptime_history, uptime_periods, uptime_alerts, pagespeed_history) support incremental syncs, fetching only records newer than the last synced timestamp. The check configuration tables are small and fully refreshed on each sync.
History tables are fetched per test, so each sync makes one request chain per test in your account. StatusCake rate limits API requests per account (60 requests per minute on free plans); the connector backs off and retries automatically, but syncs may be slow on accounts with many tests.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
uptime_tests | Uptime checks configured in your StatusCake account. | Full refresh | — | — |
uptime_history | Fetched per test, so a sync makes one request chain per test in your account. History retention on StatusCake depends on your plan | Incremental, Full refresh | created_at | — |
uptime_periods | Fetched per test, so a sync makes one request chain per test in your account. History retention on StatusCake depends on your plan | Incremental, Full refresh | created_at | — |
uptime_alerts | Fetched per test, so a sync makes one request chain per test in your account. History retention on StatusCake depends on your plan | Incremental, Full refresh | triggered_at | — |
pagespeed_tests | Pagespeed checks configured in your StatusCake account. | Full refresh | — | — |
pagespeed_history | Fetched per test, so a sync makes one request chain per test in your account. History retention on StatusCake depends on your plan | Incremental, Full refresh | created_at | — |
ssl_tests | SSL certificate checks configured in your StatusCake account, including current certificate details. | Full refresh | — | — |
heartbeat_tests | Heartbeat (push) checks configured in your StatusCake account. | Full refresh | — | — |
contact_groups | Contact groups that receive alerts from StatusCake checks. | Full refresh | — | — |
maintenance_windows | Maintenance windows during which uptime test alerts are suppressed. | Full refresh | — | — |
uptime_locations | Monitoring locations available for uptime checks — a dimension for the location field on uptime history. | Full refresh | — | — |
Troubleshooting
How much history StatusCake returns depends on your plan's data retention – records older than your plan's retention window can't be synced.
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.