Linking Gcore as a source
This source is currently in beta. It works end to end, but you may still hit rough edges. Let us know if you do.
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
The Gcore connector syncs your CDN data – resources, origin groups, SSL certificates, and hourly request and traffic statistics – into PostHog.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Gcore.
- Create an API token in the Gcore Customer Portal under API tokens. Give the token permission to read CDN data.
- Back in PostHog, enter your token in the API token field and click Next.
- Select the tables you want to sync, set the sync method and frequency, then click Import.
Once the syncs are complete, you can start using Gcore data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
resources | CDN resources and their delivery domains, status, origins, and configuration | Incremental |
origin_groups | Origin groups that supply content to CDN resources | Full refresh |
ssl_certificates | Certificates used for secure CDN delivery, including domains and validity periods | Full refresh |
cdn_requests | Hourly counts of requests to CDN edge servers, grouped by resource | Incremental |
cdn_traffic | Hourly traffic from CDN servers to clients, grouped by resource | Incremental |
Incremental tables sync only new or updated records on each run. Full refresh tables reload all data on each sync.
Statistics tables (cdn_requests and cdn_traffic) contain hourly values for completed hours, with up to 365 days of history. By default, incremental syncs look back two days to refresh recent values.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
resources | CDN resources and their delivery domains, status, origins, and configuration. | Incremental, Full refresh | updated | — |
origin_groups | Origin groups that supply content to CDN resources. | Full refresh | — | — |
ssl_certificates | Certificates used for secure CDN delivery, including their domains and validity periods. | Full refresh | — | — |
cdn_requests | Hourly counts of requests to CDN edge servers, grouped by resource. | Incremental, Full refresh | timestamp | — |
cdn_traffic | Hourly traffic from CDN servers to clients, grouped by resource. | Incremental, Full refresh | timestamp | — |
cdn_logs | Individual requests to CDN edge servers. Gcore keeps these logs for three days. | Append only, Full refresh | timestamp | — |
cdn_daily_statistics | Daily traffic, response, and cache statistics, grouped by resource and edge server region. | Incremental, Full refresh | date | — |
activity_logs | Requests made to the CDN API, such as changes to CDN resources and cache purges. | Incremental, Full refresh | requested_at | — |
purge_statuses | Cache purge requests and their results. | Incremental, Full refresh | created | — |