Skip to content

router: Set Sentry transaction field before calling the request handler #4015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

Turbo87
Copy link
Member

@Turbo87 Turbo87 commented Oct 14, 2021

This disables the router feature of sentry-conduit and instead calls set_transaction() of Sentry manually before calling the route handler itself. This has the advantage of also adding the transaction field to Sentry issues that are not reported by the sentry-conduit middleware itself.

@Turbo87 Turbo87 requested a review from locks October 14, 2021 21:49
@Turbo87 Turbo87 added the C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear label Oct 14, 2021
…dler

This disables the `router` feature of `sentry-conduit` and instead calls `set_transaction()` of Sentry manually before calling the route handler itself. This has the advantage of also adding the `transaction` field to Sentry issues that are not reported by the `sentry-conduit` middleware itself.
@Turbo87 Turbo87 force-pushed the sentry-transaction branch from 6da05e1 to c6f8c09 Compare October 18, 2021 19:52
@Turbo87
Copy link
Member Author

Turbo87 commented Oct 19, 2021

closing in favor of #4036

@Turbo87 Turbo87 closed this Oct 19, 2021
@Turbo87 Turbo87 deleted the sentry-transaction branch October 20, 2021 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backend ⚙️ C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant