Error Tracking Go
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides guidance on integrating PostHog error tracking into Go applications. It covers the essential setup, configuration of environment variables, and best practices for capturing exceptions. The skill also details how to manage issues through PostHog, including manual and automatic assignment, alerting configurations, and monitoring strategies to ensure effective error resolution.
What it does
- Guides the integration of PostHog error tracking SDK into Go applications.
- Provides best practices for using environment variables for sensitive configuration.
- Explains how to configure automatic issue assignment rules based on exception properties.
- Details how to set up alerts for new, reopened, or spiking issues via Slack, Discord, or webhooks.
- Describes how to assign issues to specific teammates or roles for better triage.
- Outlines methods for monitoring and searching issues within the PostHog dashboard.
When to use it
- When you need to implement robust error tracking in a Go-based service.
- When you want to centralize error reporting and automate issue assignment to specific teams.
- When you need to set up real-time notifications for critical application errors.
- When you need to analyze error trends or spikes to identify deployment issues.
Advantages
- Enables seamless integration with existing Go error handling patterns.
- Supports automated triage through configurable assignment rules.
- Provides flexible alerting options to keep teams informed of critical issues.
- Facilitates better debugging through stack trace analysis and issue properties.
Usage examples
- “How do I initialize PostHog error tracking in my Go application?”
- The skill instructs you to use the PostHog Go SDK, emphasizing the use of environment variables for keys and enabling autocapture for exception tracking.
- “How can I notify my team when a specific error occurs in Go?”
- You can configure alert rules in the PostHog error tracking settings to trigger notifications via Slack or webhooks based on specific exception properties.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/error-tracking-go/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip error-tracking-go.zip -d .agents/skills
Documentation by PostHog
PostHog error tracking for Go
This skill helps you add PostHog error tracking to Go applications.
Reference files
references/go.md- Go error tracking installation - docsreferences/fingerprints.md- Fingerprints - docsreferences/alerts.md- Send error tracking alerts - docsreferences/monitoring.md- Monitor and search issues - docsreferences/assigning-issues.md- Assign issues to teammates - docsreferences/upload-source-maps.md- Upload source maps - docs
Consult the documentation for API details and framework-specific patterns.
Key principles
Environment variables: Always use environment variables for PostHog keys and host URLs. Never hardcode them.
Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.
Autocapture first: Enable exception autocapture in the SDK initialization before adding manual captures.
Source maps: Upload source maps so stack traces resolve to original source code, not minified bundles.
Manual capture for boundaries: Use
captureException()at error boundaries and catch blocks for errors that don't propagate to the global handler.
Framework guidelines
No specific framework guidelines.
Files
- ATTRIBUTION.mdAdded by AutoGineer951 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md1.4 KiB
- references/alerts.md4.1 KiB
- references/assigning-issues.md5.5 KiB
- references/fingerprints.md3.4 KiB
- references/go.md4.8 KiB
- references/monitoring.md8.6 KiB
- references/upload-source-maps.md2.7 KiB
references/go.md
Go error tracking installation - Docs
1
Install the Go SDK
Required
Install the PostHog Go SDK:
Terminal
PostHog AI
go get github.com/posthog/posthog-goSource context not yet supported
The Go SDK captures stack traces with file names, line numbers, and function names, but does not yet support source context (displaying the surrounding lines of code in the error tracking UI). Symbol set uploads for Go are not currently available.
2
Initialize the client
Required
Go
PostHog AI
package main import ( "github.com/posthog/posthog-go" ) func main() { client, _ := posthog.NewWithConfig( "<ph_project_token>", posthog.Config{ Endpoint: "https://us.i.posthog.com", }, ) defer client.Close() }3
Capture exceptions
Required
There are two ways to capture exceptions with the Go SDK:
Option A: Direct capture
Use
NewDefaultExceptionto capture errors directly. This automatically generates a UUID and stack trace for you.Go
PostHog AI
import ( "time" "github.com/posthog/posthog-go" ) exception := posthog.NewDefaultException( time.Now(), "user_distinct_id", "DatabaseError", // type - rendered as title in the UI "connection refused", // value - rendered as description in the UI ) client.Enqueue(exception)For more control, build the
Exceptionstruct manually:Go
PostHog AI
import ( "time" "github.com/posthog/posthog-go" ) handled := true fingerprint := "my-custom-fingerprint" exception := posthog.Exception{ DistinctId: "user_distinct_id", Timestamp: time.Now(), ExceptionList: []posthog.ExceptionItem{ { Type: "DatabaseError", Value: "connection refused", Mechanism: &posthog.ExceptionMechanism{ Handled: &handled, }, }, }, ExceptionFingerprint: &fingerprint, } client.Enqueue(exception)Option B: Automatic capture with slog
The SDK provides a
SlogCaptureHandlerthat wraps Go's standardlog/sloglogger and automatically captures log records as exceptions.By default, it captures logs at
Warninglevel and above.Go
PostHog AI
import ( "context" "fmt" "log/slog" "os" "github.com/posthog/posthog-go" ) client, _ := posthog.NewWithConfig( "<ph_project_token>", posthog.Config{ Endpoint: "https://us.i.posthog.com", }, ) defer client.Close() baseHandler := slog.NewTextHandler(os.Stdout, &slog.HandlerOptions{ Level: slog.LevelInfo, }) logger := slog.New(posthog.NewSlogCaptureHandler(baseHandler, client, posthog.WithDistinctIDFn(func(ctx context.Context, r slog.Record) string { // Return the user ID from context or another source return "user_distinct_id" }), )) // This warning is automatically captured as an exception in PostHog logger.Warn("Something broke", "error", fmt.Errorf("connection refused"), )The handler supports several configuration options:
Option Description Default WithMinCaptureLevel(level) Minimum log level to capture slog.LevelWarn WithDistinctIDFn(fn) Function to extract distinct ID from context/record Returns "" (skips capture) WithFingerprintFn(fn) Custom fingerprint for error grouping nil (PostHog assigns) WithSkip(n) Stack frames to skip 5 WithStackTraceExtractor(e) Custom stack trace extractor DefaultStackTraceExtractor WithDescriptionExtractor(e) Custom description extractor ErrorExtractor Error extraction
The slog handler automatically extracts error descriptions from log attributes with keys
errorerror(case-insensitive). It also supports wrapped errors via theUnwrap()interface.4
Verify error tracking
Recommended
Trigger a test exception to confirm events are being sent to PostHog. You should see them appear in the activity feed.
Go
PostHog AI
exception := posthog.NewDefaultException( time.Now(), "test_user", "TestError", "This is a test exception from Go", ) client.Enqueue(exception) // Flush the queue before exiting client.Close()
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/error-tracking/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 error-tracking-go.zip