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.
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
fix: Log4j configurations and wording #11395
fix: Log4j configurations and wording #11395
Changes from 1 commit
4c06f9e
6400455
269ac21
35e3e61
b6521e2
e17118d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a particular reason for adding the
level
here, compared to the original?Do you want to highlight the possibility of overriding the level like in
docs/platforms/java/common/legacy/log4j2/index.mdx
? If so, I would suggest to also add a comment here, like in the mentioned file.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lbloder, earlier the snippet was as follows:
Though this didn't capture the configuration stated at the beginning of the
java.log4j2.mdx
file:That is, sending
ERROR
s (and of higher severity) to Sentry was misconfigured – I fixed it.I am not able to follow you. I fixed
legacy/log4j2/index.mdx
too, since that document was stating:Hence, AFAIC, all configurations now match what is stated to be expected from them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vy Sorry for the confusion.
Thank you, for fixing this, I just looked at the differences in the xml and thus overlooked the fact that the description was wrong in the first place.
Large diffs are not rendered by default.