AutoGineer
Generated banner for Logs Datadog
Generated logo for Logs Datadog

Logs Datadog

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

PostHog logs for Datadog
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides the configuration steps to forward logs from Datadog-compatible exporters directly to PostHog. By redirecting your log traffic to PostHog's ingestion endpoint, you can centralize system logs alongside your product analytics and session replays, enabling deeper correlation between system behavior and user activity.

What it does

  • Configures Datadog Agents to forward logs to PostHog
  • Provides the specific ingestion endpoint for Datadog-formatted logs
  • Offers guidance on using environment variables for secure token management
  • Supports integration with existing Datadog log exporters
  • Enables verification of log flow into the PostHog interface

When to use it

  • When you want to consolidate system logs into your PostHog project
  • When you are already using Datadog log exporters and want to add PostHog as a destination
  • When you need to correlate backend system logs with frontend user sessions
  • When you want to leverage PostHog's log search and analysis features

Advantages

  • Minimal configuration changes required for existing Datadog setups
  • Centralizes logs alongside product analytics and session replays
  • Maintains compatibility with standard Datadog log formats
  • Uses secure environment variable-based authentication

Usage examples

“How do I point my Datadog agent to PostHog?”
You will be guided to set the DD_LOGS_CONFIG_LOGS_DD_URL environment variable to the PostHog Datadog-compatible endpoint using your project token.
“Where do I find my project token for log ingestion?”
The skill directs you to your PostHog Project Settings to retrieve your project token (starting with phc_).

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/logs-datadog/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip logs-datadog.zip -d .agents/skills

Documentation by PostHog

PostHog logs for Datadog

This skill helps you add PostHog log ingestion to Datadog applications.

Reference files

  • references/datadog.md - Datadog logs installation - docs

  • references/start-here.md - Getting started with logs - docs

  • references/search.md - Search logs - docs

  • references/best-practices.md - Logging best practices - docs

  • references/troubleshooting.md - Logs troubleshooting - docs

  • references/link-session-replay.md - Link session replay - docs

  • references/debug-logs-mcp.md - Debug logs with mcp - docs

Consult the documentation for API details and framework-specific patterns.

Key principles

  • Environment variables: Always use environment variables for PostHog keys and OpenTelemetry endpoints. Never hardcode them.

  • Minimal changes: Add log export alongside existing logging. Don't replace or restructure existing logging code.

  • OpenTelemetry: PostHog logs use the OpenTelemetry protocol. Configure an OTLP exporter pointed at PostHog's ingest endpoint.

  • Structured logging: Prefer structured log formats with key-value properties over plain text messages.

Framework guidelines

No specific framework guidelines.

Files

references/datadog.md

Datadog logs installation - Docs

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. 1

    Get your project token

    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 with phx_).

    You can find your project token in Project Settings.

  2. 2

    Configure Datadog Agent

    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. 3

    Other Datadog log exporters

    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. 4

    Test your setup

    Recommended

    Once everything is configured, test that logs are flowing into PostHog:

    1. Restart the Datadog Agent (or your log forwarder) to apply the configuration

    2. Generate some log entries in your application

    3. Check the PostHog logs interface for your log entries

    4. Verify the logs appear in your project

    View your logs in PostHog

  5. Next steps

    Checkpoint

    What you can do with your logs

    ActionDescription
    Why you need logsWhat logs show you that nothing else does
    Search logsUse the search interface to find specific log entries
    Filter by levelFilter by INFO, WARN, ERROR, etc.
    Link session replayConnect logs to users and session replays by passing posthogDistinctId and sessionId
    Logging best practicesLearn what to log, how to structure logs, and patterns that make logs useful in production

    Troubleshoot common issues

Community questions

Ask a question

Was this page useful?

HelpfulCould be better

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
PostHog
Publisher
PostHog (Official)
Source
PostHog/skills · skills/posthog/logs/skills/datadog · commit a5d30e7
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
PostHog/skills

AutoGineer is not affiliated with or endorsed by PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download logs-datadog.zip