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://mp-staging.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/start-here.md

Getting started with logs - Docs

New to logging? Read Why you need logs first for a primer on what logs show you that nothing else does.

Install and configure logging

PostHog logs is a powerful logging solution that works with the OpenTelemetry Protocol (OTLP). You don't need any vendor specific SDKs – just use standard OpenTelemetry libraries.

Install and configure your logging client to send logs to PostHog:

  • Use the HTTP endpoint: https://us.i.posthog.com/i/v1/logs

  • Authenticate with your project token (the same token used for events/exceptions)

  • Include the token in the Authorization header or as a ?token= query parameter

  • Use the standard OTLP log format

Configure your logging client

Search and analyze your logs

Once your logs are flowing into PostHog, you can:

  • Search through logs using multiple search tokens, negative filters, and exact phrase matching

  • Filter by time ranges to find specific events

  • Correlate logs with events from your PostHog analytics

Navigate to the Logs section in your PostHog dashboard to start exploring your log data.

Learn how to search logs

Troubleshooting

Common issues you might encounter when setting up logging:

  • Authentication errors - Make sure you're using your correct project token

  • Connection issues - Verify the HTTP endpoint is accessible

  • Log format problems - Ensure you're using the standard OTLP log format

Troubleshoot common issues

Logging best practices

Learn what to log, how to structure your logs, and the patterns that make logs actually useful in production – including wide events, strategic sampling, and adding business context.

Read the best practices guide

1/4

Install and configure logging RequiredSearch and analyze your logs RequiredTroubleshooting RecommendedLogging best practices Recommended

Install and configure logging

Required

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.

Download ZIP

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