-
Notifications
You must be signed in to change notification settings - Fork 222
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
Add The Ability To Set Log Level #55
Comments
would it be good to make a PR in pulsar for this? |
pgier
pushed a commit
to pgier/pulsar-helm-chart
that referenced
this issue
Apr 22, 2022
rdhabalia
pushed a commit
to rdhabalia/pulsar-helm-chart
that referenced
this issue
Feb 2, 2023
…r. (apache#55) * test bookie logs on ebs * add persistent volume to ebs * zookeeper ebs changes for testing * zookeeper ebs changes for testing * zookeeper ebs changes for testing * zookeeper ebs changes for testing * zookeeper ebs changes for testing * zookeeper ebs changes for testing * zookeeper ebs changes for testing * zookeeper ebs changes for testing * zookeeper ebs changes for testing * adding default values
maybe just set these environment variables in values.yaml broker configData:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Setting PULSAR_LOG_ROOT_LEVEL and PULSAR_ROOT_LOGGER environment variables using configData does not change the log level since it uses the conf/log4j2.yaml .
Describe the solution you'd like
Ideally we would be able to only use environment variables, but that will not be possible until pulsar does not depend on the log4j2.yaml file. To get it working in its current state, we could create a ConfigMap with the contents of the logfile, then mount it as a volume and set the PULSAR_LOG_CONF to point to our mounted file instead of conf/log4j2.yaml.
The text was updated successfully, but these errors were encountered: