feat: adopt PostHog error tracking via captureException#346
Open
feat: adopt PostHog error tracking via captureException#346
Conversation
Send $exception events alongside existing tool_called events when tool calls fail. This gives us PostHog's built-in issue grouping, stack traces, lifecycle management, and alerting — without losing our custom domain metadata (error_phase, error_category, http_status, etc.). Also consolidates secret redaction into a single before_send hook that covers both regular events and SDK-built exception events.
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
$exceptionevents via PostHog'scaptureExceptionAPI when tool calls fail, enabling built-in issue grouping, stack traces, lifecycle management, and alertingerror_phase,error_category,http_status,is_retryable, etc.) as additional properties so PostHog issues carry our contextbefore_sendhook covering bothtool_calledevents and SDK-built$exceptionevents — previously this was done inline incaptureEventtool_calledevents unchanged for usage analytics;$exceptionfires in addition, not insteadTest plan
pnpm type-checkpasses$exceptionevents appear in PostHog error tracking dashboardtool_calledand$exceptionevents