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
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/logs-python/downloadUnzip 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 - docsreferences/start-here.md- Getting started with logs - docsreferences/search.md- Search logs - docsreferences/best-practices.md- Logging best practices - docsreferences/troubleshooting.md- Logs troubleshooting - docsreferences/link-session-replay.md- Link session replay - docsreferences/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 posthogorpip install -r requirements.txtand do NOT use unquoted version specifiers like>=directly in shell commandsIn 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
- ATTRIBUTION.mdAdded by AutoGineer933 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.4 KiB
- references/best-practices.md19.6 KiB
- references/debug-logs-mcp.md2.2 KiB
- references/link-session-replay.md4.9 KiB
- references/python.md3.6 KiB
- references/search.md2.5 KiB
- references/start-here.md2.4 KiB
- references/troubleshooting.md3.5 KiB
references/search.md
Search logs - Docs
The logs search accepts multiple tokens and quoted phrases to help you find the exact log lines you need.
Space-separated words are combined with implicit AND: the log must contain all positive tokens
Prefix a token with
!to exclude logs that contain that token. You can use multiple negative tokens to exclude several different termsWrap text in double quotes to search for an exact phrase (an exact substring match)
How to use search
Require multiple words
Type: bug frontend
Result: Shows logs that contain both the words bug and frontend anywhere in the line.
Exclude words
Type: error !timeout
Result: Shows logs that contain error but excludes any log that also contains timeout.
Combine require + exclude
Type: api "server error" !403 !timeout
Result: Must contain api and the exact phrase server error, and must not contain 403 or timeout.
Search exact phrases
Type: "failed to connect"
Result: Matches logs that include the substring failed to connect exactly as written.
More examples
| Query | What it finds |
|---|---|
| login timeout | Logs that contain both login and timeout |
| login !debug | Logs that contain login and excludes logs that contain debug |
| "database error" | Logs with the exact phrase database error |
| "payment failed" !trace !debug | Logs that contain the exact phrase payment failed and excludes any that contain trace or debug |
Tips
Special characters: If a token contains spaces or special characters, wrap it in double quotes to treat it as a single search item
Standalone exclamation mark: A standalone
!by itself is ignored — use!followed by text to exclude that textMultiple negative tokens: List multiple
!tokens(e.g.,!debug !trace) to exclude logs that contain any of those tokensPunctuation: Quotes and escapes are handled using shell-like parsing rules, so complex tokens should be quoted if they contain spaces or special characters
Get more from search with structured logs
Search works best when your logs are consistent and structured. Adding key-value context like user_id, endpoint, and status_code to every log line makes filtering faster and more precise. See our logging best practices guide for patterns that make logs easier to search and query.
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.
Related skills
Claude API
AnthropicOfficial
Comprehensive reference for integrating Anthropic's Claude API, SDKs, and Managed Agents into your applications.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0Medium riskHas scriptsGitHub stars of the source repository188.6k
Transformers
K-Dense· Community
Integrate Hugging Face Transformers for model loading, inference, and fine-tuning across NLP, vision, and audio tasks.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskGitHub stars of the source repository56.4k
Open Notebook
K-Dense· Community
Integrate with the self-hosted Open Notebook platform to automate research ingestion, context-aware chat, and AI-driven analysis.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskHas scriptsGitHub stars of the source repository56.4k
Vision Sft
Seth Hobson· Community
A structured workflow for supervised fine-tuning of vision-language models, focusing on adapter configuration and silent failure prevention.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
LLM Evaluation
Seth Hobson· Community
A comprehensive framework for evaluating LLM application performance using automated metrics, human feedback, and LLM-as-a-judge techniques.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Lora Qlora Recipes
Seth Hobson· Community
Provides configuration recipes and best-practice hyperparameters for LoRA and QLoRA supervised fine-tuning.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download logs-python.zip