Linking UptimeRobot as a source
This source is currently in alpha. The interface and available tables may change.
The UptimeRobot source syncs your uptime monitoring data – monitors, downtime event logs, response-time history, alert contacts, maintenance windows, and public status pages – into PostHog, so you can report on availability SLAs and downtime trends alongside your product data.
Prerequisites
You need an UptimeRobot account on any plan. The API is available on the free plan.
You also need a main account API key. We recommend using the read-only API key, found under Integrations & API in your UptimeRobot dashboard.
Monitor-specific API keys only grant access to a single monitor, so the alert contacts, maintenance windows, and status pages tables won't sync with one.
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 UptimeRobot, you'll need:
- API key – your main account API key (read-only recommended), found under Integrations & API in the UptimeRobot dashboard.
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.
Monitor event logs and response times support incremental sync on their datetime field. Response times are fetched in 7-day windows, and only the last 30 days are synced on the initial run.
The remaining tables (monitors, alert contacts, maintenance windows, and status pages) are small and sync as a full refresh each run.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
monitors | A monitored endpoint (website, ping, port, keyword, or heartbeat check) with its current status and uptime ratios. | Full refresh | — | — |
monitor_logs | Up/down/pause event history per monitor. Incremental syncs only fetch logs newer than the last synced event | Incremental, Full refresh | datetime | — |
response_times | Response-time samples per monitor, fetched in 7-day windows. Only syncs the last 30 days on initial sync | Incremental, Full refresh | datetime | — |
alert_contacts | Contacts notified when a monitor changes state (email, SMS, webhook, Slack, etc.). | Full refresh | — | — |
maintenance_windows | Scheduled maintenance windows during which monitors pause and alerts are suppressed. | Full refresh | — | — |
status_pages | Public status pages (PSPs) that display the status of selected monitors. | Full refresh | — | — |
Troubleshooting
- UptimeRobot rate-limits API calls per plan (10 requests per minute on the free plan). Syncs automatically back off and retry when rate-limited, so accounts with many monitors on the free plan may sync slowly.
- If your API key is invalid or has been revoked, generate a new read-only API key under Integrations & API in your UptimeRobot dashboard, then reconnect.
- Monitor-specific API keys only access a single monitor. If tables like alert contacts, maintenance windows, or status pages aren't syncing, make sure you're using a main account API key.
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.