Labsco
PostHog logo

error-tracking-go

★ 49

by posthog · part of posthog/skills

PostHog error tracking for Go

🔥🔥🔥FreeQuick setup
#analytics#git
🧩 One of 7 skills in the posthog/skills package — works on its own, and pairs well with its siblings.

This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.

name: error-tracking-go description: PostHog error tracking for Go metadata: author: PostHog version: 1.9.4

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 - docs
  • references/fingerprints.md - Fingerprints - docs
  • references/alerts.md - Send error tracking alerts - docs
  • references/monitoring.md - Monitor and search issues - docs
  • references/assigning-issues.md - Assign issues to teammates - docs
  • references/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.