Linking Honeycomb 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 Honeycomb connector syncs datasets, columns, derived columns, 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 Honeycomb configuration API key to pull your Honeycomb observability configuration - datasets, SLOs, burn alerts, triggers, markers, boards, and more - .
You can create a configuration key under Environment settings → API keys in your Honeycomb account. Grant read access for the resources you want to sync: Manage Queries and Columns, Manage SLOs, Manage Triggers, Manage Markers, Manage Boards, and Manage Recipients.
Keys are region-specific - pick the region that matches your Honeycomb account.
You'll be asked for:
- Configuration API key: for example
Configuration key. - Region: choose between US (api.honeycomb.io) and EU (api.eu1.honeycomb.io).
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 Honeycomb tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Configuration API key | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
datasets | A dataset in the environment: a named collection of events sharing a schema, the unit most Honeycomb resources are scoped to. | Full refresh | — | — |
columns | A queryable column in a dataset's schema, created automatically as events with new fields arrive. | Full refresh | — | — |
derived_columns | Includes environment-wide rows under the all dataset slug alongside per-dataset rows. | Full refresh | — | — |
slos | A service level objective: a target percentage of qualified events matching a service level indicator over a rolling time period. Multi-dataset SLOs are listed once per dataset they span. | Full refresh | — | — |
burn_alerts | One row per burn alert per dataset, fetched by walking every dataset's SLOs. | Full refresh | — | — |
triggers | A trigger: a scheduled query with a threshold that notifies recipients when crossed. | Full refresh | — | — |
markers | Includes environment-wide rows under the all dataset slug alongside per-dataset rows. | Full refresh | — | — |
boards | A board: a saved collection of queries and visualizations for a team or service. | Full refresh | — | — |
recipients | Credential-bearing recipient fields (integration keys, webhook URLs and secrets) are redacted during sync. | Full refresh | — | — |
board_views | A saved view on a board: a named set of filters applied to every query on the board. | Full refresh | — | — |
slo_counts_history | Hourly good and bad event counts per SLO. Requires the Honeycomb Enterprise plan with SLO counts history enabled for your team. | Incremental, Full refresh | start_time | — |
Troubleshooting
- If the connection fails with an authorization error, the configuration API key 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.