Skip to content
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

Refactor converting HttpServletRequest to Sentry Request in Spring integration. #1387

Merged
merged 6 commits into from
Apr 14, 2021

Conversation

maciejwalkowiak
Copy link
Contributor

📜 Description

Convert HttpServletRequest to Sentry Request once for all events triggered during request execution.

💡 Motivation and Context

Currently conversion from HttpServletRequest to Sentry request happens for each event in the event processor. With this change we do it only once. Also as a result, there is no need to set the request on the scope in the SentryTracingFilter.

💚 How did you test it?

📝 Checklist

  • I reviewed the submitted code
  • I added tests to verify the changes
  • I updated the docs if needed
  • No breaking changes

Copy link
Contributor

@marandaneto marandaneto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@maciejwalkowiak maciejwalkowiak merged commit 73f512e into main Apr 14, 2021
@maciejwalkowiak maciejwalkowiak deleted the refactor-scope-request branch April 14, 2021 10:09
@@ -171,6 +173,7 @@ This release brings the Sentry Performance feature to Java SDK, Spring, Spring B
* Enhancement: Add the ability to register multiple OptionsConfiguration beans (#1093)
* Fix: Append DebugImage list if event already has it
* Fix: Sort breadcrumbs by Date if there are breadcrumbs already in the event
* Feat: Database query tracing with datasource-proxy (#1095)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was reverted, should not be here

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.

2 participants