Honeycomb
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.
Connect Honeycomb to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Enter a Honeycomb configuration API key to pull your Honeycomb observability configuration — datasets, SLOs, burn alerts, triggers, markers, boards, and more — into the PostHog Data warehouse.
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.
Configuration
| Option | Type | Required |
|---|---|---|
Configuration API key | password | Yes |
Region | select | Yes |
Linking Honeycomb to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Honeycomb
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
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 | — | — |