Linking STRATO as a source
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.
Contents
This source is currently in alpha. The interface and available tables may change.
The STRATO connector syncs servers, snapshots, images, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
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.
Sync your STRATO ServerCloud resources, such as servers, snapshots, images, storage, networking, and users.
This source covers the STRATO ServerCloud product only. To get an API token, open the STRATO CloudPanel, go to Management > Users, select or create a user, enable API access, and copy the API key.
You'll be asked for:
- API token
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.
All STRATO tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Servers | Cloud servers in the STRATO ServerCloud account, with hardware, image, IP, and status details. | Full refresh | — | — |
Snapshots | Snapshots of each cloud server. | Full refresh | — | — |
Images | Server images, including operating system details and backup frequency. | Full refresh | — | — |
BlockStorages | Block storage volumes and the server each one is attached to. | Full refresh | — | — |
SharedStorages | Shared storage volumes with CIFS/NFS paths and attached servers. | Full refresh | — | — |
FirewallPolicies | Firewall policies with their rules and the server IPs they are assigned to. | Full refresh | — | — |
LoadBalancers | Load balancers with health check settings, rules, and assigned server IPs. | Full refresh | — | — |
PublicIps | Public IP addresses and the resource each one is assigned to. | Full refresh | — | — |
PrivateNetworks | Private networks and the servers assigned to each one. | Full refresh | — | — |
Vpns | VPNs configured in the account. | Full refresh | — | — |
MonitoringPolicies | Monitoring policies with thresholds, monitored ports and processes, and assigned servers. | Full refresh | — | — |
SshKeys | SSH public keys registered in the account and the servers using them. | Full refresh | — | — |
Users | CloudPanel users with their roles and API access settings. The API key itself is removed before rows are stored. | Full refresh | — | — |
Roles | CloudPanel roles with their permissions and assigned users. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.