Linking DigitalOcean 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.
This source is currently in alpha. The interface and available tables may change.
The DigitalOcean connector syncs droplets, apps, kubernetes clusters, 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.
Enter a DigitalOcean personal access token to pull your DigitalOcean infrastructure and billing data.
Create a token under API → Tokens with at least Read scope.
You'll be asked for:
- Personal access token: for example
dop_v1_....
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 DigitalOcean tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Personal access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
droplets | Virtual machines (Droplets) running in your account. | Full refresh | — | — |
apps | App Platform applications and their current specification. | Full refresh | — | — |
actions | Account-wide log of actions taken on resources (creates, resizes, power cycles, transfers). | Full refresh | — | — |
kubernetes_clusters | DigitalOcean Kubernetes (DOKS) clusters. | Full refresh | — | — |
databases | Managed database clusters (Postgres, MySQL, Redis, MongoDB, Kafka). | Full refresh | — | — |
volumes | Block storage volumes. | Full refresh | — | — |
snapshots | Snapshots of Droplets and volumes. | Full refresh | — | — |
load_balancers | Load balancers distributing traffic across Droplets. | Full refresh | — | — |
projects | Projects used to organize resources in your account. | Full refresh | — | — |
vpcs | Virtual Private Cloud networks. | Full refresh | — | — |
images | User-owned images (snapshots, backups, and custom images). | Full refresh | — | — |
domains | DNS domains managed by DigitalOcean. | Full refresh | — | — |
ssh_keys | SSH public keys registered on the account. | Full refresh | — | — |
reserved_ips | Reserved (formerly floating) IP addresses. | Full refresh | — | — |
tags | Tags used to label and group resources. | Full refresh | — | — |
sizes | Catalog of Droplet size plans, with the resources and price each slug maps to. | Full refresh | — | — |
regions | Catalog of data center regions, resolving the region slugs carried by other resources. | Full refresh | — | — |
invoices | Billing invoices for the account. | Full refresh | — | — |
billing_history | Append-only ledger of billing events (invoices, payments, credits). | Full refresh | — | — |
invoice_items | Line items behind each invoice, attributing spend to the resource that incurred it. | Full refresh | — | — |
invoice_summaries | Per-invoice totals, split into product charges, overages, taxes, and credits. | Full refresh | — | — |
project_resources | Membership table mapping each resource URN to the project it is assigned to. | Full refresh | — | — |
domain_records | DNS records configured under each domain in the account. | Full refresh | — | — |
database_backups | Backups available for each managed database cluster. Caching and Valkey clusters have none. | Full refresh | — | — |
database_events | Event log for each managed database cluster, covering creates, updates, maintenance, and power cycles. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the personal access 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.