Setting the file. One moment.
Subchapter 49.3
references/datadog.mdMarkdown3 KBView on GitHub
If you’re already using Datadog to collect logs, you can forward them to PostHog by configuring your existing Datadog log exporters (like the Datadog Agent) to send logs to PostHog’s Datadog-compatible endpoint.
1
Required
You’ll need your PostHog project token to authenticate log requests. This is the same key you use for capturing events and exceptions with the PostHog SDK.
Important: Use your project token which starts with
phc_. Do not use a personal token (which starts withphx_).
You can find your project token in Project Settings (opens in a new tab).
2
Required
Set the Datadog logs URL to point to PostHog’s Datadog-compatible endpoint. The endpoint format is:
PostHog AI
https://us.i.posthog.com/i/v1/logs/datadog/<ph_project_token>For the Datadog Agent, set the DD_LOGS_CONFIG_LOGS_DD_URL environment variable:
Terminal
PostHog AI
export DD_LOGS_CONFIG_LOGS_DD_URL="https://us.i.posthog.com/i/v1/logs/datadog/<ph_project_token>"Alternatively, you can set this in your datadog.yaml configuration file:
YAML
PostHog AI
logs_config:
logs_dd_url: "https://us.i.posthog.com/i/v1/logs/datadog/<ph_project_token>"3
Optional
If you’re using other Datadog log exporters or forwarders, configure them to send logs to the same endpoint:
PostHog AI
https://us.i.posthog.com/i/v1/logs/datadog/<ph_project_token>The endpoint accepts logs in the standard Datadog log format, so existing integrations should work without additional changes.
4
Recommended
Once everything is configured, test that logs are flowing into PostHog:
Checkpoint
What you can do with your logs
| Action | Description |
|---|---|
| Why you need logs (opens in a new tab) | What logs show you that nothing else does |
| Search logs (opens in a new tab) | Use the search interface to find specific log entries |
| Filter by level | Filter by INFO, WARN, ERROR, etc. |
| Link session replay (opens in a new tab) | Connect logs to users and session replays by passing posthogDistinctId and sessionId |
| Link logs to a person (opens in a new tab) | Surface every log emitted on behalf of a user on their PostHog person profile |
| Logging best practices (opens in a new tab) | Learn what to log, how to structure logs, and patterns that make logs useful in production |
Ask a question
HelpfulCould be better