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

# Linking Datadog as a source

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

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

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](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

Connect your Datadog account to sync logs, events, monitors, dashboards, and more into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Datadog.
3.  Create an **API key** and an **application key** in your [Datadog organization settings](https://app.datadoghq.com/organization-settings/api-keys). Grant the application key read scopes for the data you want to sync, for example `dashboards_read`, `monitors_read`, `incident_read`, `slos_read`, `synthetics_read`, and `user_access_read`. Also note your **Datadog site** (for example US1 `datadoghq.com`, US3, US5, EU1 `datadoghq.eu`, AP1, or US1-FED `ddog-gov.com`).
4.  Back in PostHog, select your **Datadog site**, enter the **API key** and **Application key**, then click **Next**.
5.  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 Datadog data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `logs` | Log events (limited to your account's retention window on initial sync) | Incremental |
| `audit_logs` | Audit log events (limited to your account's retention window on initial sync) | Incremental |
| `events` | Events (limited to your account's retention window on initial sync) | Incremental |
| `dashboards` | Dashboards | Full refresh |
| `monitors` | Monitors | Full refresh |
| `users` | Users | Full refresh |
| `incidents` | Incidents | Full refresh |
| `slos` | Service level objectives | Full refresh |
| `synthetic_tests` | Synthetic tests | Full refresh |
| `downtimes` | Downtimes | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Sync limitations

Logs, audit logs, and events read access is governed by your Datadog account's data retention, so the first sync can only reach back as far as your account's retention window allows.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Datadog site` | select | Yes |
| `API key` | password | Yes |
| `Application key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `logs` | Limited to your Datadog account's retention window on initial sync | Incremental, Full refresh | timestamp | — |
| `audit_logs` | Limited to your Datadog account's retention window on initial sync | Incremental, Full refresh | timestamp | — |
| `events` | Limited to your Datadog account's retention window on initial sync | Incremental, Full refresh | timestamp | — |
| `usage_hourly` | Hourly usage for one product family, for one organization. | Incremental, Full refresh | timestamp | — |
| `usage_summary` | Daily usage across every billing dimension, aggregated over all organizations in the account. | Incremental, Full refresh | date | — |
| `usage_historical_cost` | Final cost per month, per organization. Datadog publishes a month by the 16th of the month after it. | Incremental, Full refresh | date | — |
| `error_tracking_issues` | A grouped error from Datadog Error Tracking, combining APM traces, logs, and RUM. The table is rebuilt on every sync from the last 14 days of activity, so it holds issues with errors in that window. | Full refresh | — | — |
| `error_spans` | Limited to your Datadog account's retention window on initial sync | Incremental, Full refresh | start\_timestamp | — |
| `error_logs` | Limited to your Datadog account's retention window on initial sync | Incremental, Full refresh | timestamp | — |
| `monitor_alerts` | Limited to your Datadog account's retention window on initial sync | Full refresh | — | — |
| `dashboards` | A Datadog dashboard — a configurable set of widgets visualizing metrics and logs. | Full refresh | — | — |
| `monitors` | A monitor that watches a metric, log, or check and alerts when conditions are met. | Full refresh | — | — |
| `users` | A user account in the Datadog organization. | Full refresh | — | — |
| `incidents` | An incident tracked in Datadog Incident Management. | Full refresh | — | — |
| `slos` | A service level objective (SLO) defining a reliability target over a time window. | Full refresh | — | — |
| `synthetic_tests` | A Synthetic monitoring test (API or browser test) that probes endpoints or flows. | Full refresh | — | — |
| `downtimes` | A scheduled downtime that mutes monitor alerts over a time window. | Full refresh | — | — |
| `metrics` | A metric name that has actively reported data to Datadog in the lookback window. | Full refresh | — | — |
| `usage_billable_summary` | Billable usage for one organization over one billing period. | Full refresh | — | — |
| `usage_estimated_cost` | Estimated cost for the current and previous month. Datadog delays it by up to 72 hours from when the cost was incurred. | Full refresh | — | — |
| `slo_corrections` | A correction that excludes a time window from an SLO's error budget, for example a maintenance window. | Full refresh | — | — |
| `slo_history` | Error-budget history for one SLO over the synced window, including its SLI value against each configured threshold. | Full refresh | — | — |
| `teams` | A Datadog team, the owner handle attached to monitors, incidents, SLOs and services. | Full refresh | — | — |
| `team_memberships` | A user's membership of a team, including the role they hold in it. | Full refresh | — | — |