Increase Sentry frame limit#284
Open
jivanf wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
What was changed
Increased the frame limit to 250 frames in the Sentry page.
Why?
The frames shown in the Sentry page are currently limited to 10 frames. When the cause of an exception is after these 10 frames, one has to find the frame in the issue's JSON data. This frequently happens in frameworks like Laravel where there's usually at least 100 frames in a stack trace and the culprit is beyond the first 10 frames.
I'm using this branch in a Laravel project and haven't seen any issues.
Checklist