Linking Fastly 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 Fastly connector syncs current user, services, service versions, 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 your Fastly API token to automatically pull your Fastly account and service configuration.
You can create an API token in your Fastly account settings.
A read-only token with global scope is sufficient to sync every table.
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 Fastly 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 |
|---|---|---|---|---|
current_user | The user whose API token authenticates this connection. | Full refresh | — | — |
services | Every Fastly service in the account. | Full refresh | — | — |
service_versions | All configuration versions for each service. | Full refresh | — | — |
service_domains | Domains attached to each service's active version. | Full refresh | — | — |
service_backends | Origin backends configured on each service's active version. | Full refresh | — | — |
service_acls | Access control lists on each service's active version. | Full refresh | — | — |
service_dictionaries | Edge dictionaries on each service's active version. | Full refresh | — | — |
acl_entries | The IP addresses and subnet ranges held in each service's ACLs. | Full refresh | — | — |
dictionary_items | The key/value rows held in each service's edge dictionaries. | Full refresh | — | — |
historical_stats | Daily traffic, cache hit ratio, bandwidth and error counts for every service. | Incremental, Full refresh | Bucket start | — |
origin_inspector | Daily origin latency, status code and byte counts per origin host, for services with Origin Inspector enabled. | Incremental, Full refresh | Bucket start | — |
service_authorizations | Which users can reach which services, and the permission each one holds. | Full refresh | — | — |
pops | Every Fastly POP, with the datacenter codes used in stats and origin metrics. | Full refresh | — | — |
invoices | Posted invoices for the account, with the line items billed on each. | Full refresh | — | — |
billing_usage_metrics | Usage per product and service over the most recent billing months. | 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.