Limit cases where SQL origin is captured #881
Merged
Conversation
This file contains 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
cleptric
approved these changes
Apr 11, 2024
There was a problem hiding this comment.
Docs and 
Besides https://docs.sentry.io/platforms/php/guides/laravel/configuration/laravel-options/, there is also https://docs.sentry.io/product/performance/queries/. Can be one PR.
# Conflicts: # src/Sentry/Laravel/Integration.php
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.
Adds option to only capture origin for queries slower than a threshold (100 ms by default).
Also limit the frames to 20 when trying to detect an in-app frame that is considered the origin for an event.