AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides the necessary guidelines and patterns for implementing PostHog error tracking within Python applications. It covers SDK initialization, best practices for capturing exceptions, and how to leverage PostHog's platform features for monitoring, alerting, and assigning issues to team members. The guide emphasizes secure data handling, such as avoiding PII in event properties, and ensures proper SDK lifecycle management to prevent event loss.
What it does
- Guides the installation and configuration of the PostHog Python SDK.
- Provides patterns for enabling automatic exception capture.
- Explains how to manually capture exceptions at error boundaries.
- Details how to configure alerts for new or spiking issues.
- Outlines methods for assigning issues to specific users or roles.
- Instructs on uploading source maps for readable stack traces.
When to use it
- When you need to monitor and track runtime exceptions in a Python application.
- When you want to automate the triage and assignment of software errors.
- When you need to set up real-time alerts for critical application failures.
- When you are integrating PostHog into a new or existing Python project.
Advantages
- Centralizes error reporting and management within the PostHog platform.
- Supports automated issue assignment based on custom rules.
- Provides clear guidelines on avoiding PII in event data.
- Ensures reliable event flushing with proper SDK shutdown procedures.
Usage examples
- “How do I initialize the PostHog client in my Python script to track exceptions?”
- The agent provides a code snippet using the Posthog() constructor with enable_exception_autocapture=True and an atexit.register() call for the shutdown method.
- “How can I alert my team when a specific error spikes in volume?”
- The agent explains how to configure spike alerts in the PostHog error tracking settings to monitor error rates against historical baselines.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/error-tracking-python/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip error-tracking-python.zip -d .agents/skills
Documentation by PostHog
PostHog error tracking for Python
This skill helps you add PostHog error tracking to Python applications.
Reference files
references/python.md- Python error tracking installation - docsreferences/fingerprints.md- Fingerprints - docsreferences/alerts.md- Send error tracking alerts - docsreferences/monitoring.md- Monitor and search issues - docsreferences/assigning-issues.md- Assign issues to teammates - docsreferences/upload-source-maps.md- Upload source maps - docs
Consult the documentation for API details and framework-specific patterns.
Key principles
Environment variables: Always use environment variables for PostHog keys and host URLs. Never hardcode them.
Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.
Autocapture first: Enable exception autocapture in the SDK initialization before adding manual captures.
Source maps: Upload source maps so stack traces resolve to original source code, not minified bundles.
Manual capture for boundaries: Use
captureException()at error boundaries and catch blocks for errors that don't propagate to the global handler.
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 AutoGineer963 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.5 KiB
- references/alerts.md4.1 KiB
- references/assigning-issues.md5.5 KiB
- references/fingerprints.md3.4 KiB
- references/monitoring.md8.6 KiB
- references/python.md5.1 KiB
- references/upload-source-maps.md2.7 KiB
references/python.md
Python error tracking installation - Docs
1
Install the package
Required
Install the PostHog Python library using pip:
Terminal
PostHog AI
pip install posthog2
Initialize PostHog
Required
Initialize the PostHog client with your project token and host from your project settings:
Python
PostHog AI
from posthog import Posthog posthog = Posthog( project_api_key='<ph_project_token>', host='https://us.i.posthog.com' )Django integration
If you're using Django, check out our Django integration for automatic request tracking.
3
Send events
Recommended
Once installed, PostHog will automatically start capturing events. You can also manually send events to test your integration:
Capture custom events by calling the
capturemethod with an event name and properties:Python
PostHog AI
import posthog posthog.capture('user_123', 'user_signed_up', properties={'example_property': 'example_value'})Verify PostHog is initialized
Recommended
Before proceeding, enable debug and call
posthog.capture('test_event')to make sure you can capture events.4
Setting up exception autocapture
Recommended
Exception autocapture can be enabled during initialization of the PostHog client to automatically capture any unhandled exceptions thrown by your Python application. It works by setting Python's built-in exception hooks, such as
sys.excepthookandthreading.excepthook.Python
PostHog AI
from posthog import Posthog posthog = Posthog("<ph_project_token>", enable_exception_autocapture=True, ...)We recommend setting up and using contexts so that exceptions automatically include distinct IDs, session IDs, and other properties you can set up with tags.
You can also enable code variables capture to automatically capture the state of local variables when exceptions occur, giving you a debugger-like view of your application.
5
Manually capturing exceptions
Optional
For exceptions handled by your application that you would still like sent to PostHog, you can manually call the capture method:
Python
PostHog AI
posthog.capture_exception(e, distinct_id="user_distinct_id", properties=additional_properties)You can find a full example of all of this in our Python (and Flask) error tracking tutorial.
6
Framework-specific exception capture
Optional
Python frameworks often have built-in error handlers. This means PostHog's default exception autocapture won't work and we need to manually capture errors instead. The exact process depends on the framework:
Django
The Python SDK provides a Django middleware that automatically wraps all requests with a context. Add the middleware to your Django settings:
Python
PostHog AI
MIDDLEWARE = [ # ... other middleware 'posthog.integrations.django.PosthogContextMiddleware', # ... other middleware ]By default, the middleware captures exceptions and sends them to PostHog. Disable with
POSTHOG_MW_CAPTURE_EXCEPTIONS = False. UsePOSTHOG_MW_EXTRA_TAGS,POSTHOG_MW_REQUEST_FILTER, andPOSTHOG_MW_TAG_MAPto customize. See the Django integration docs for full configuration.Flask
Python
PostHog AI
from flask import Flask, jsonify from posthog import Posthog posthog = Posthog('<ph_project_token>', host='https://us.i.posthog.com') @app.errorhandler(Exception) def handle_exception(e): event_id = posthog.capture_exception(e) response = jsonify({'message': str(e), 'error_id': event_id}) response.status_code = 500 return responseFastAPI
Python
PostHog AI
from fastapi.responses import JSONResponse from posthog import Posthog posthog = Posthog('<ph_project_token>', host='https://us.i.posthog.com') @app.exception_handler(Exception) async def http_exception_handler(request, exc): posthog.capture_exception(exc) return JSONResponse(status_code=500, content={'message': str(exc)})Verify error tracking
Recommended
Confirm events are being sent to PostHog
Before proceeding, let's make sure exception events are being captured and sent to PostHog. You should see events appear in the activity feed.
Image: Activity feed with eventsImage: Activity feed with events
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/error-tracking/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.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download error-tracking-python.zip