AutoGineer
Generated banner for Logs Go
Generated logo for Logs Go

Logs Go

PostHogOfficialCreated by PostHog

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

From the author

PostHog logs for Go
— 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 integrating PostHog log ingestion into Go applications. It emphasizes the use of the OpenTelemetry (OTLP) protocol to send structured logs to PostHog, ensuring that system activity is captured effectively without disrupting existing logging infrastructure. The skill covers implementation principles, such as using environment variables for configuration and adopting wide-event logging patterns to improve observability and debuggability.

What it does

  • Provides instructions for setting up PostHog log ingestion in Go projects.
  • Outlines best practices for structured logging and wide-event generation.
  • Explains how to configure OTLP exporters for PostHog endpoints.
  • Offers guidance on integrating logs with other PostHog features like session replays.
  • Supports debugging workflows via the Model Context Protocol (MCP).

When to use it

  • When you need to centralize logs from Go services into PostHog.
  • When you want to transition from plain text logging to structured, queryable events.
  • When you need to correlate system logs with user sessions and product analytics.
  • When you are setting up observability for production Go applications.

Advantages

  • Enables unified observability by placing logs alongside product analytics and session replays.
  • Promotes high-signal logging through structured wide-event patterns.
  • Maintains compatibility with existing logging code by supporting side-by-side export.
  • Facilitates AI-assisted debugging through MCP integration.

Usage examples

“How do I configure my Go application to send logs to PostHog using OpenTelemetry?”
The agent provides the necessary steps to set up an OTLP exporter in your Go code, pointing it to the PostHog ingest endpoint using environment variables.
“What is the best way to log payment processing in my Go backend?”
The agent suggests moving away from step-by-step logs toward a single, rich 'wide event' containing relevant metadata like order ID, duration, and user ID.

Install

  1. Download the skill as a ZIP:

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

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

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

Documentation by PostHog

PostHog logs for Go

This skill helps you add PostHog log ingestion to Go applications.

Reference files

  • references/go.md - Go 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/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

QueryWhat it finds
login timeoutLogs that contain both login and timeout
login !debugLogs that contain login and excludes logs that contain debug
"database error"Logs with the exact phrase database error
"payment failed" !trace !debugLogs 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.

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