Skip to content

Isolate Sentry context per FastStream message - #409

Merged
lesnik512 merged 1 commit into
mainfrom
fix/387-faststream-sentry-scope
Nov 3, 2026
Merged

lesnik512 merged 1 commit into
mainfrom
fix/387-faststream-sentry-scope

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Closes #387.

  • Open a Sentry isolation scope per FastStream message when Sentry is configured.
  • Verify that the failing message’s captured event retains its own tag and breadcrumb and excludes the preceding message’s context.

The regression failed before the fix. All 607 tests, lint, and type checking passed. A local middleware lifecycle microbenchmark measured about 2.34 µs of overhead per message.

@lesnik512
lesnik512 merged commit 128b59d into main Nov 3, 2026
35 checks passed
@lesnik512
lesnik512 deleted the fix/387-faststream-sentry-scope branch November 3, 2026 04:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Give each FastStream message its own Sentry isolation scope

1 participant