Exclude frames from stacktrace in structured json #47550
+64
−20
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
Signed-off-by: michaldo <[email protected]>
spring-projects-issues
added
the
status: waiting-for-triage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Allows declare by application properties which frames should be excluded from stacktrace.
For a long time it is widely known stacktrace contains frames from frameworks (haha) which are irrelevant for bug tracking and decrease readability.
For example this 13 years old article https://nurkiewicz.com/2012/03/filtering-irrelevant-stack-trace-lines.html is still valid.
More links can be found here: #43864 (comment)
And here #42486
Current printer implemented in Spring Boot has everything to filter out irrelevant frames. The only missing piece is configuring irrelevant frames.
This is PR is the icing on the cake.