AutoGineer
Generated banner for Logs Other
Generated logo for Logs Other

Logs Other

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

PostHog logs for Other Languages
— the description by PostHog

AutoGineer summary

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

This skill provides guidance and best practices for configuring log ingestion into PostHog for applications written in languages other than those with native SDK support. It emphasizes the use of OpenTelemetry (OTLP) to export structured logs, ensuring that system telemetry is captured effectively without requiring significant changes to existing logging infrastructure. The skill focuses on shifting from verbose, step-by-step logging to wide, context-rich events that facilitate easier debugging and analysis.

What it does

  • Provides instructions for configuring OTLP exporters to send logs to PostHog.
  • Outlines best practices for structured logging to improve queryability and reduce noise.
  • Explains how to differentiate between user-centric events and system-centric logs.
  • Offers guidance on using environment variables for secure configuration of ingestion endpoints.
  • Supports integration with AI-driven debugging tools via the PostHog MCP server.

When to use it

  • When you need to centralize logs from applications that lack specific PostHog SDK support.
  • When you want to adopt structured logging patterns to make production debugging more efficient.
  • When you are setting up observability for services that need to correlate logs with session replays or feature flags.
  • When you are transitioning from verbose, step-level logging to canonical wide events.

Advantages

  • Enables unified observability by placing logs alongside product analytics and session replays.
  • Promotes the use of industry-standard OpenTelemetry protocols.
  • Reduces storage costs and query complexity by encouraging structured, high-value log events.
  • Facilitates easier correlation between system errors and specific user sessions.

Usage examples

“How do I configure my application to send logs to PostHog using OpenTelemetry?”
The agent provides the necessary OTLP exporter configuration steps and environment variable requirements to point your application logs to the PostHog ingest endpoint.
“What is the best way to structure my logs for better debugging?”
The agent explains the 'wide event' pattern, providing a JSON example that includes trace context, business attributes, and relevant metadata to replace granular, low-value log lines.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/posthog/logs-other/download

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

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

Documentation by PostHog

PostHog logs for Other Languages

This skill helps you add PostHog log ingestion to Other Languages applications.

Reference files

  • 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

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

No specific framework guidelines.

Files

references/debug-logs-mcp.md

Debug Logs with MCP - Docs

The PostHog MCP server gives AI agents direct access to your Logs. Ask your agent to search, filter, and analyze log data without leaving your code editor.

With MCP, your agents can:

  • Search and filter logs – Query by severity level, service name, date range, and free text.

  • Discover log attributes – List available attributes and their values to build targeted queries.

  • Debug in context – Investigate production issues without switching tools.

  • Correlate with traces – Use trace IDs and span IDs from log entries to follow request flows across services.

This works in any MCP client – Cursor, Windsurf, Claude Code, and others.

Example prompts

Try these prompts with your MCP-enabled agent:

  • Show me all error logs from the last hour.

  • What services are logging errors? Search for error logs from the payments service.

  • Find logs related to trace ID abc123.

  • What log attributes are available? Show me the values for the service.name attribute.

  • Show me warning and error logs from the last 24 hours, excluding debug noise.

Logs tools

The MCP server provides three tools for working with logs:

ToolDescription
logs-querySearch and query logs with filters for severity levels (trace, debug, info, warn, error, fatal), service names, date ranges, and free text. Supports pagination for large result sets.
logs-list-attributesList available log attributes in your project to discover what you can filter on. Supports filtering by attribute type (log or resource).
logs-list-attribute-valuesGet possible values for a specific log attribute. Find service names, log levels, or other attribute values before querying.

A typical workflow:

  1. Call logs-list-attributes to discover available filter attributes.

  2. Call logs-list-attribute-values to find specific values (e.g., which service names exist).

  3. Call logs-query to search logs with the right filters.

Get started

See the MCP server documentation for setup instructions.

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.

Security

No issues found by our static scan· No issues found

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/other · 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-other.zip