Linking Pingdom as a source
This source is currently in alpha. The interface and available tables may change.
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
The Pingdom connector syncs your uptime monitoring data into PostHog, including checks, probes, maintenance windows, and alerts.
Creating a Pingdom API token
Pingdom uses Bearer token authentication. A read-only token is sufficient for syncing data into PostHog.
- Log in to My Pingdom.
- Go to Settings > Pingdom API.
- Click Add API token, give it a name, and select read access.
- Copy the token.
For more details, see Pingdom's API documentation.
Linking Pingdom
- Go to the Data pipeline sources page in PostHog.
- Click + New source and then click Link next to Pingdom.
- Paste your Pingdom API token.
- Click Next, choose the tables you want to sync, and then click Import.
Once the sync completes, you can query your Pingdom data directly in PostHog.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
checks | An uptime check that monitors the availability of a host or service from Pingdom. | Full refresh | — | — |
probes | A Pingdom probe server that runs checks from a specific geographic location. | Full refresh | — | — |
maintenance | A scheduled maintenance window during which checks are paused. | Full refresh | — | — |
alerts | An alert action triggered by a check state change, such as a notification sent to a user. | Incremental, Full refresh | time | — |
Sync modes
Pingdom tables use different sync strategies depending on whether the Pingdom API supports filtering by time:
- Full refresh - The
checks,probes, andmaintenancetables are re-downloaded on every sync. These are small dimension tables and the Pingdom API doesn't expose an "updated since" filter for them. - Incremental - The
alertstable supports incremental syncing. PostHog uses thefromUNIX timestamp filter on the/actionsendpoint to only fetch alerts newer than the last sync.
Available datasets and endpoints
| Dataset | Endpoint path | Sync mode | Primary key |
|---|---|---|---|
checks | /checks | Full refresh | id |
probes | /probes | Full refresh | id |
maintenance | /maintenance | Full refresh | id |
alerts | /actions | Incremental | checkid, time, userid, via |
All endpoints use the Pingdom API 3.1 (api.pingdom.com/api/3.1).
The alerts table uses a composite primary key because individual alert rows don't have a unique identifier. Duplicate rows with the same key combination are tolerated by the pipeline.