Generated banner for Logs Python
Generated logo for Logs Python

Logs Python

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • Low risk

From the author

PostHog logs for Python
— the description by PostHog

AutoGineer summary

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

This skill provides guidelines and patterns for integrating PostHog log ingestion into Python applications. It emphasizes using the OpenTelemetry protocol for structured logging, ensuring that logs are centralized and actionable. The skill covers configuration requirements, such as using environment variables for sensitive data, and provides specific implementation patterns for the Python SDK to ensure proper event capture and resource management.

What it does

  • Provides patterns for structured logging using OpenTelemetry.
  • Outlines requirements for Python SDK configuration and initialization.
  • Explains how to manage log lifecycle and resource cleanup in Python scripts.
  • Offers guidance on distinguishing between events and logs for better observability.
  • Details how to use MCP tools to search and query logs within development environments.
  • Provides best practices for log content to improve queryability and reduce noise.

When to use it

  • When you need to centralize logs from Python applications into PostHog.
  • When implementing structured logging to improve production debugging.
  • When migrating from event-based tracking to dedicated log ingestion for system events.
  • When setting up AI agents to query and analyze production logs via MCP.

Advantages

  • Enables correlation between logs, product analytics, and session replays.
  • Promotes the use of wide events for more efficient log analysis.
  • Ensures consistent handling of sensitive data by separating PII from event properties.
  • Supports integration with AI-assisted debugging workflows.

Usage examples

“How do I initialize the PostHog Python SDK for logging?”
The agent provides the constructor pattern using the Posthog class, including the enable_exception_autocapture=True setting and instructions to use environment variables for keys.
“Show me how to search for error logs using MCP.”
The agent explains the use of the logs-query tool, including how to filter by severity level and service name.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/posthog/logs-python/download
  2. Unzip it into the cross-client skills folder of your project:

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

Documentation by PostHog

PostHog logs for Python

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

Reference files

  • references/python.md - Python 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

  • Remember that source code is available in the venv/site-packages directory

  • posthog is the Python SDK package name

  • Install dependencies with pip install posthog or pip install -r requirements.txt and do NOT use unquoted version specifiers like >= directly in shell commands

  • In CLIs and scripts: MUST call posthog.shutdown() before exit or all events are lost

  • Always use the Posthog() class constructor (instance-based API) instead of module-level posthog.api_key config

  • Always include enable_exception_autocapture=True in the Posthog() constructor to automatically track exceptions

  • NEVER send PII in capture() event properties — no emails, full names, phone numbers, physical addresses, IP addresses, or user-generated content

  • PII belongs in identify() person properties, NOT in capture() event properties. Safe event properties are metadata like message_length, form_type, boolean flags.

  • Register posthog_client.shutdown with atexit.register() to ensure all events are flushed on exit

  • The Python SDK has NO identify() method — use posthog_client.set(distinct_id=user_id, properties={...}) to set person properties, or use identify_context(user_id) within a context

Files

references/python.md

Python logs installation - Docs

  1. 1

    Install OpenTelemetry packages

    Required

    Terminal

    PostHog AI

    pip install opentelemetry-api opentelemetry-sdk opentelemetry-exporter-otlp
  2. 2

    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 API key (which starts with phx_).

    You can find your project token in Project Settings.

  3. 3

    Configure the SDK

    Required

    Set up the OpenTelemetry SDK to send logs to PostHog.

    Python

    PostHog AI

    from opentelemetry import logs
    from opentelemetry.sdk.logs import LoggerProvider, LoggingHandler
    from opentelemetry.sdk.logs.export import BatchLogRecordProcessor
    from opentelemetry.exporter.otlp.proto.http._log_exporter import OTLPLogExporter
    # Configure the logger provider
    logger_provider = LoggerProvider()
    logs.set_logger_provider(logger_provider)
    # Create OTLP exporter with API key in header
    otlp_exporter = OTLPLogExporter(
        endpoint="https://us.i.posthog.com/i/v1/logs",
        headers={"Authorization": "Bearer <ph_project_token>"}
    )
    # Add processor
    logger_provider.add_log_record_processor(
        BatchLogRecordProcessor(otlp_exporter)
    )
    # Get logger
    logger = logs.get_logger("my-app")

    Alternatively, you can pass the API key as a query parameter:

    Python

    PostHog AI

    otlp_exporter = OTLPLogExporter(
        endpoint="https://us.i.posthog.com/i/v1/logs?token=<ph_project_token>"
    )
  4. 4

    Use OpenTelemetry logging

    Required

    Now you can start logging with OpenTelemetry:

    Python

    PostHog AI

    import logging
    # Configure logging to use OpenTelemetry
    logging.basicConfig(level=logging.INFO)
    logging.getLogger().addHandler(LoggingHandler())
    # Use standard Python logging
    logger = logging.getLogger("my-app")
    logger.info("User action", extra={"userId": "123", "action": "login"})
    logger.warning("Deprecated API used", extra={"endpoint": "/old-api"})
    logger.error("Database connection failed", extra={"error": "Connection timeout"})
  5. 5

    Test your setup

    Recommended

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

    1. Send a test log from your application

    2. Check the PostHog logs interface for your log entries

    3. Verify the logs appear in your project

    View your logs in PostHog

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

Needs: Needs an API key, Needs Python

Security

What our scanner noticed· Low risk

  • Instructions that use the network

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/python · 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 or PostHog.

Download ZIP

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