Repository navigation
docs(exception-metadata): register the .NET runtime and ASP.NET Core capture sources - #218
Draft
posthog[bot] wants to merge 1 commit into
Draft
posthog[bot] wants to merge 1 commit into
posthog[bot] wants to merge 1 commit into
Conversation
…capture sources posthog-dotnet#356 ships opt-in runtime exception capture and the ASP.NET Core request-context middleware, emitting three $exception_source values the canonical registry did not list. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Generated-By: PostHog Desktop Task-Id: ceb308d7-ee12-4fcc-8c48-2523e744421b
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
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.
Why
The SDK watcher loop found drift between the
exception-event-metadataspec and the SDKs. The canonical$exception_sourcetable fixes the first-party value for each capture boundary so two SDKs cannot name the same boundary differently — but it listed no .NET value at all, and posthog-dotnet now emits three.Source change
PostHogOptions.CaptureUnhandledExceptions, defaultfalse) emittingdotnet.appdomain_unhandled_exceptionanddotnet.task_scheduler_unobserved_task_exception, and has the ASP.NET Core request-context middleware emitaspnetcore.request_context_middlewarefor both an escaping failure and one a downstream error handler consumed. The PR names this spec as the contract it follows.What changed
Change
2026-11-13-register-dotnet-exception-sources, applied and archived in this PR:$exception_sourcetable.Naming rationale is in
design.md—aspnetcore.*for the framework integration (matchingdjango.middleware/rails.middleware),dotnet.*for the two CLR hooks, kept separate because their handled/level outcomes differ.Uncertainty
None material. The convention clause already permitted these values, so no SDK becomes non-conformant either way; this only records them.
Touches the same table as the open #196 and #209 (Ruby rows), so expect a trivial merge conflict if those land first.
Created with PostHog Desktop
🤖 Generated with Claude Code