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
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/logs-go/downloadUnzip 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 - 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 - 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
- ATTRIBUTION.mdAdded by AutoGineer921 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md1.2 KiB
- references/best-practices.md19.6 KiB
- references/debug-logs-mcp.md2.2 KiB
- references/go.md4.0 KiB
- references/link-session-replay.md4.9 KiB
- references/search.md2.5 KiB
- references/start-here.md2.4 KiB
- references/troubleshooting.md3.5 KiB
references/go.md
Go logs installation - Docs
1
Install OpenTelemetry packages
Required
Terminal
PostHog AI
go get go.opentelemetry.io/otel/sdk/log go get go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp2
Get your project token
Required
You'll need your PostHog project token to authenticate log requests. This is the same key you use for capturing events and exceptions with the PostHog SDK.
Important: Use your project token which starts with
phc_. Do not use a personal API key (which starts withphx_).You can find your project token in Project Settings.
3
Configure the SDK
Required
Set up the OpenTelemetry SDK to send logs to PostHog.
Go
PostHog AI
package main import ( "os" "context" "log" "log/slog" "go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp" "go.opentelemetry.io/otel/exporters/stdout/stdoutlog" "go.opentelemetry.io/contrib/bridges/otelslog" otellog "go.opentelemetry.io/otel/sdk/log" "go.opentelemetry.io/otel/log/global" ) func main() { ctx := context.Background() // Create OTLP HTTP exporter exporter, err := otlploghttp.New(ctx, otlploghttp.WithEndpoint("us.i.posthog.com"), otlploghttp.WithURLPath("/i/v1/logs"), otlploghttp.WithHeaders(map[string]string{ "Authorization": "Bearer <ph_project_token>", }), ) if err != nil { panic(err) } // you could also set this outside your application os.Setenv("OTEL_SERVICE_NAME", "my-service") stdoutExporter, _ := stdoutlog.New() // Create logger provider loggerProvider := otellog.NewLoggerProvider( otellog.WithProcessor(otellog.NewBatchProcessor(exporter)), // optional, also log to stdout otellog.WithProcessor(otellog.NewSimpleProcessor(stdoutExporter)), ) defer func() { loggerProvider.Shutdown(context.Background()) }() global.SetLoggerProvider(loggerProvider) slog.SetDefault(otelslog.NewLogger("")) log.Println("this is a log line") }Alternatively, you can pass the API key as a query parameter by modifying the URL path:
Go
PostHog AI
otlploghttp.WithURLPath("/i/v1/logs?token=<ph_project_token>")4
Use OpenTelemetry logging
Required
Now you can start logging with OpenTelemetry:
Go
PostHog AI
import ( "go.opentelemetry.io/otel/log" ) logger := otel.GetLoggerProvider().Logger("my-app") logger.Info(ctx, "User action", log.String("userId", "123"), log.String("action", "login"), )5
Test your setup
Recommended
Once everything is configured, test that logs are flowing into PostHog:
Send a test log from your application
Check the PostHog logs interface for your log entries
Verify the logs appear in your project
Next steps
Checkpoint
What you can do with your logs
Action Description Why you need logs What logs show you that nothing else does Search logs Use the search interface to find specific log entries Filter by level Filter by INFO, WARN, ERROR, etc. Link session replay Connect logs to users and session replays by passing posthogDistinctId and sessionId Logging best practices Learn what to log, how to structure logs, and patterns that make logs useful in production
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.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download logs-go.zip