feat: integrate PostHog error tracking with logger#649
Merged
Conversation
- Add error hook system to Pino logger that captures error/fatal logs - Create initPostHogErrorTracking() to connect logger to PostHog - Remove duplicate captureException call in global error handler - Add rate limiting (100ms) and deduplication (5s window) to prevent flooding - Use addEventListener instead of window.onerror to not overwrite handlers - Add try-catch around PostHog client initialization All logger.error() calls are now automatically captured to PostHog with module context and stack traces when POSTHOG_API_KEY is configured. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
initPostHogErrorTracking()to connect logger to PostHogcaptureExceptioncall in global error handler (was capturing twice)addEventListenerinstead ofwindow.onerrorto not overwrite existing handlersHow it works
All
logger.error()calls are now automatically captured to PostHog with module context and stack traces whenPOSTHOG_API_KEYis configured. This means you'll see all server-side errors in PostHog without any additional instrumentation.Test plan
🤖 Generated with Claude Code