Omnibus Instrument Logs — Agent Skill by PostHog

From the author

Add PostHog log capture to track application logs. Use after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. Also handles initial OTLP exporter setup if not yet configured.

— the description by PostHog

AutoGineer summary

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

This skill provides a structured approach to instrumenting applications for log collection via PostHog. It guides the user through detecting their current logging stack, installing necessary OpenTelemetry SDKs, configuring OTLP exporters, and ensuring logs are enriched with structured properties for better observability. It also supports forwarding existing Datadog logs to PostHog, ensuring that developers can centralize their system logs alongside product analytics and session replays.

What it does

Detects the application's language, framework, and existing logging infrastructure.
Configures OpenTelemetry OTLP exporters to send logs to PostHog.
Integrates log capture alongside existing logging handlers without replacing them.
Promotes the use of structured, key-value based logging for better searchability.
Sets up environment variables for secure API key and endpoint management.
Provides a path to forward existing Datadog log streams to PostHog.

When to use it

When you need to start capturing application logs in PostHog for the first time.
After implementing new features or reviewing pull requests to ensure relevant events are logged.
When you want to transition from plain text logging to structured, queryable logs.
When you need to integrate PostHog logging into an existing Datadog-based setup.

Advantages

Centralizes system logs with product analytics and session replays.
Uses industry-standard OpenTelemetry protocols for broad compatibility.
Maintains existing logging architecture by adding exporters as a sidecar or secondary output.
Encourages best practices like wide-event logging for easier debugging.

Usage examples

“Set up PostHog log capture for my Node.js application.”: The agent will analyze the project, install the required OpenTelemetry packages, configure the OTLP exporter, and guide you through setting the necessary environment variables.
“I am already using Datadog for logs, how do I send them to PostHog?”: The agent will provide instructions to update your Datadog agent configuration to point to the PostHog Datadog-compatible ingest endpoint.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/omnibus-instrument-logs/download

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

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

Documentation by PostHog

Add PostHog log capture

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.

Supported platforms: Next.js, Node.js, Python, Go, Java, Datadog, and any language via OpenTelemetry.

Instructions

Follow these steps IN ORDER:

STEP 1: Analyze the codebase and detect the platform.

Detect the language, framework, and existing logging setup.
Look for log libraries (winston, pino, logging module, logrus, log4j, serilog, etc.).
Look for lockfiles to determine the package manager.
Check for existing PostHog log export setup. If the OTLP exporter is already configured, skip to STEP 5 to add log capture for new code.

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

Install the OpenTelemetry SDK and OTLP exporter packages for the detected platform.
Do not manually edit dependency files — use the package manager's install command.
Always install packages as a background task. Don't await completion; proceed with other work immediately.

STEP 4: Configure the OTLP exporter. (Skip if PostHog log export is already configured.)

PostHog logs use the OpenTelemetry protocol. Set up an OTLP exporter pointed at PostHog's ingest endpoint.
Follow the platform-specific reference for the exact configuration.

STEP 5: Integrate with existing logging.

Add the PostHog log exporter alongside existing logging. Don't replace existing log handlers or outputs.
Do not alter the fundamental architecture of existing files. Make additions minimal and targeted.
You must read a file immediately before attempting to write it.

STEP 6: Add structured properties.

Ensure logs include structured key-value properties for filtering and search in PostHog.
Prefer structured log formats with key-value properties over plain text messages.

STEP 7: Set up environment variables.

If an env-file-tools MCP server is connected, use check_env_keys then set_env_values to configure the PostHog API key, host, and OpenTelemetry endpoint.
Reference these environment variables in code instead of hardcoding them.

Reference files

references/nextjs.md - Next.js logs installation - docs
references/nodejs.md - Node.js logs installation - docs
references/python.md - Python logs installation - docs
references/go.md - Go logs installation - docs
references/java.md - Java logs installation - docs
references/datadog.md - Datadog logs installation - docs
references/other.md - Other languages 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

Each platform reference contains specific OTLP configuration, SDK setup, and integration patterns. Find the one matching the user's stack.

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.

Files

ATTRIBUTION.mdAdded by AutoGineer939 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md4.4 KiB
references/best-practices.md19.6 KiB
references/datadog.md3.0 KiB
references/debug-logs-mcp.md2.2 KiB
references/go.md4.0 KiB
references/java.md3.9 KiB
references/link-session-replay.md4.9 KiB
references/nextjs.md5.5 KiB
references/nodejs.md3.6 KiB
references/other.md2.7 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 terms
Wrap 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 text
Multiple negative tokens: List multiple !tokens (e.g., !debug !trace) to exclude logs that contain any of those tokens
Punctuation: 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 MCP server, 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.

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 more
Apache-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 more
MITLow 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 more
MITLow 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 more
MITGitHub 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 more
MITGitHub 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 more
MITGitHub stars of the source repository42.3k

Download ZIP

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