> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Honeybadger as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/honeybadger

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Honeybadger connector syncs your error monitoring data – projects, errors (faults), error occurrences (notices), deployments, and uptime checks – into PostHog, so you can track error rates across environments and correlate error spikes with releases.

## Prerequisites

You need a Honeybadger account and your personal authentication token, available on your [Honeybadger profile page](https://app.honeybadger.io/users/edit). The token grants read access to every project your Honeybadger user can see.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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.

When linking Honeybadger, you'll need:

-   **Personal authentication token** – found on your [Honeybadger profile page](https://app.honeybadger.io/users/edit) under **Authentication 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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

We recommend incremental sync for the `faults`, `notices`, and `deploys` tables. Honeybadger's API allows 360 requests per hour with at most 25 rows per page, so full refreshes of large accounts are slow – incremental syncs only fetch what changed since the last run.

The `notices` table is disabled by default because it is fetched one fault at a time, which can use up the API quota quickly on accounts with many errors. Enable it if you need per-occurrence detail such as request context and backtraces.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Personal authentication token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `projects` | A container that holds all your Honeybadger data for a single app or service. | Full refresh | — | — |
| `faults` | An error ('fault') grouping many individual occurrences (notices). Called an error in the Honeybadger UI. | Incremental, Full refresh | created\_at, last\_notice\_at | — |
| `notices` | One row per error occurrence. Fetched per fault, so syncing large accounts is slow against Honeybadger's 360 requests/hour limit — prefer incremental sync | Incremental, Full refresh | created\_at | — |
| `deploys` | A deployment recorded for a project, used to correlate errors with releases. | Incremental, Full refresh | created\_at | — |
| `sites` | An uptime check ('site') configured for a project. | Full refresh | — | — |
| `environments` | An environment (e.g. production, staging) that errors in a project are grouped by. | Full refresh | — | — |
| `occurrences` | Daily error occurrence counts per project. Honeybadger only serves the most recent month, so each sync replaces it; use the notices table for older history | Full refresh | — | — |
| `affected_users` | Users affected by each error, with an occurrence count per user. Fetched per fault, so syncing large accounts is slow against Honeybadger's 360 requests/hour limit — prefer incremental sync | Incremental, Full refresh | fault\_last\_notice\_at | — |
| `outages` | A period during which an uptime check ('site') was down. | Incremental, Full refresh | created\_at | — |
| `uptime_checks` | One row per uptime check result, per site and location. Frequent checks produce many rows, so syncing is slow against Honeybadger's 360 requests/hour limit. Prefer incremental sync | Incremental, Full refresh | created\_at | — |
| `comments` | Comments on each error. Fetched per fault with no time filter, so every sync is slow against Honeybadger's 360 requests/hour limit | Full refresh | — | — |
| `check_ins` | A check-in that monitors a cron job or scheduled task, with its current state. | Full refresh | — | — |
| `alarm_history` | State changes of each Honeybadger Insights alarm | Full refresh | — | — |

## Troubleshooting

If a sync fails with an access denied error, your authentication token is invalid or was revoked – copy a fresh token from your Honeybadger profile page and update the source credentials.

Syncs that hit Honeybadger's 360 requests/hour rate limit pause and retry automatically, so a large initial backfill can take several hours to complete.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.