Add log level configuration in pulsar-client #8195
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
jiazhai
approved these changes
Oct 4, 2020
|
/pulsarbot run-failure-checks |
codelipenghui
approved these changes
Oct 4, 2020
|
/pulsarbot run-failure-checks |
wolfstudy
pushed a commit
that referenced
this pull request
Oct 30, 2020
### Motivation When using pulsar-client CLI, we have a lot of log4j logs useless for just sending/receiving messages. It could great to not display these logs with just a env variable (like in pulsar-admin). ### Modifications The log level can be configured with the system property `pulsar.log.level` for the Java application. The modification is the ability to set this level using a env variable PULSAR_LOG_LEVEL (default: info). (cherry picked from commit c6550e4)
huangdx0726
pushed a commit
to huangdx0726/pulsar
that referenced
this pull request
Nov 13, 2020
### Motivation When using pulsar-client CLI, we have a lot of log4j logs useless for just sending/receiving messages. It could great to not display these logs with just a env variable (like in pulsar-admin). ### Modifications The log level can be configured with the system property `pulsar.log.level` for the Java application. The modification is the ability to set this level using a env variable PULSAR_LOG_LEVEL (default: info).
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.
Motivation
When using pulsar-client CLI, we have a lot of log4j logs useless for just sending/receiving messages.
It could great to not display these logs with just a env variable (like in pulsar-admin).
Modifications
The log level can be configured with the system property
pulsar.log.levelfor the Java application.The modification is the ability to set this level using a env variable PULSAR_LOG_LEVEL (default: info).
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
Documentation