Linking Mezmo 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 Mezmo connector (formerly LogDNA) syncs your telemetry pipeline configurations, component alerts, and pipeline health data into the PostHog data warehouse, so you can analyze your observability setup alongside your product data.
Prerequisites
You need a Mezmo account with access to Telemetry Pipelines. You also need permission to create API keys under Settings > Organization > API Keys.
Create a service account and generate an IAM access key with read access to pipelines and alerts. If you're using an enterprise key, you also need the delegated account ID for the target account.
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.
When linking Mezmo, you'll need:
IAM access key – create a service account in Mezmo under Settings > Organization > API Keys. The key starts with
sts_and must have read access to pipelines and alerts.Delegated account ID (optional) – required only for enterprise keys. Enter the account ID you want to query on behalf of.
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 Mezmo tables use full refresh sync. Each run reloads all data from the Mezmo API. The Mezmo v3 API doesn't support pagination or server-side time filters, so incremental sync isn't available.
Available tables
| Table | Description | Sync method |
|---|---|---|
pipelines | Telemetry pipelines in your Mezmo account. | Full refresh |
alerts | Alert configurations attached to pipeline components. These are alert definitions, not alert history. | Full refresh |
pipeline_health | Current source health for active, published pipelines over the default 15-minute interval. | Full refresh |
Configuration
| Option | Type | Required |
|---|---|---|
IAM access key | password | Yes |
Delegated account ID | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
pipelines | Telemetry pipelines in the Mezmo account. | Full refresh | — | — |
alerts | Alert configurations attached to pipeline components. | Full refresh | — | — |
pipeline_health | Current source health for active, published pipelines over the default 15-minute interval. | Full refresh | — | — |
Troubleshooting
- If Mezmo rejects your access key, create a new IAM access key under Settings > Organization > API Keys and reconnect.
- If you see a permission error, check that your key has read access to pipelines and alerts. For enterprise keys, verify the delegated account ID is correct.
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.