From posthog
Adds PostHog log capture for application logs, ensuring structured properties. Handles initial OTLP exporter setup. Use after implementing features or reviewing PRs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/posthog:instrument-logsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to add PostHog log capture for new or changed code. Use it after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. If PostHog log export is not yet configured, this skill also covers initial OTLP exporter setup. Supports any platform or language.
references/android.mdreferences/best-practices.mdreferences/datadog.mdreferences/debug-logs-mcp.mdreferences/flutter.mdreferences/go.mdreferences/ios.mdreferences/java.mdreferences/link-session-replay.mdreferences/nextjs.mdreferences/nodejs.mdreferences/other.mdreferences/python.mdreferences/react-native.mdreferences/search.mdreferences/start-here.mdreferences/troubleshooting.mdUse this skill to add PostHog log capture for new or changed code. Use it after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. If PostHog log export is not yet configured, this skill also covers initial OTLP exporter setup. Supports any platform or language.
Supported platforms: Next.js, Node.js, Python, Go, Java, Datadog, Android, React Native, iOS, and any language via OpenTelemetry.
Follow these steps IN ORDER:
STEP 1: Analyze the codebase and detect the platform.
STEP 2: Research log capture. (Skip if PostHog log export is already configured.) 2.1. Find the reference file below that matches the detected platform — it is the source of truth for OTLP exporter configuration and integration with existing logging. Read it now. 2.2. If no reference matches, use the "Other Languages" reference as a fallback — it covers the generic OpenTelemetry approach.
STEP 3: Install dependencies. (Skip if PostHog log export is already configured.)
STEP 4: Configure the OTLP exporter. (Skip if PostHog log export is already configured.)
STEP 5: Integrate with existing logging.
STEP 6: Add structured properties.
STEP 7: Set up environment variables.
.env, .env.local, or framework-specific env files). If valid values already exist, skip this step.projects-get tool to retrieve the project's api_token. If multiple projects are returned, ask the user which project to use. If the MCP server is not connected or not authenticated, ask the user for their PostHog project API key instead.https://us.i.posthog.com for US Cloud or https://eu.i.posthog.com for EU Cloud.https://us.i.posthog.com/v1 (US) or https://eu.i.posthog.com/v1 (EU).references/nextjs.md - Next.js logs installation - docsreferences/nodejs.md - Node.js logs installation - docsreferences/python.md - Python logs installation - docsreferences/go.md - Go logs installation - docsreferences/java.md - Java logs installation - docsreferences/datadog.md - Datadog logs installation - docsreferences/android.md - Android logs installation - docsreferences/react-native.md - React native logs installation - docsreferences/ios.md - Ios logs installation - docsreferences/flutter.md - Flutter logs installation - docsreferences/other.md - Other languages 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 - docsEach platform reference contains specific OTLP configuration, SDK setup, and integration patterns. Find the one matching the user's stack.
npx claudepluginhub anthropics/claude-plugins-official --plugin posthogInstruments apps with Logfire observability for traces, logs, metrics using Python, JavaScript/TypeScript, Rust SDKs and OpenTelemetry. Handles FastAPI, Django, Express, LLM calls correctly.
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".
Instruments services with OpenTelemetry for RED metrics, structured logs, distributed tracing, and health checks. Outputs code/config for detected stacks like Node.js, Python, Go. Use for 'add monitoring', 'instrument', 'observability'.