Configure logging on standalone

[Samreay]

Hi all,

I've been struggling with getting the logging to be manageable when running pulsar standalone for unit testing purposes. By default, running a

docker run -it -p 6650:6650 -p 8080:8080  --tmpfs /pulsar/data apachepulsar/pulsar:3.1.0 bin/pulsar standalone

Gives pages and pages of logs like this:

I haven't found any environment variables that work to control the logging at all, so right now our docker run has morphed into something that I'd consider... unsavoury.

docker run -it -p 6650:6650 -p 8080:8080  --tmpfs /pulsar/data apachepulsar/pulsar:3.1.0 /bin/bash -c "sed -i 's/info/error/g' /pulsar/conf/log4j2.yaml && sed -i 's/INFO/ERROR/g' /pulsar/conf/log4j2.yaml && sed -i 's/"\$\{sys:pulsar.log.level\}/error/g"' /pulsar/conf/log4j2.yaml && bin/pulsar standalone"

Which gives us something that doesn't make scrolling through logs when this runs in CI (and all the services are mixed together) a complete nightmare:

But I presume there has to be a better way of silencing non-error logs than a bunch of sed commands. Does anyone know how to do this?

[jak78]

Hi!
You can use the PULSAR_LOG_LEVEL env variable:

docker run -it -p 6650:6650 -p 8080:8080 -e PULSAR_LOG_LEVEL=ERROR --tmpfs /pulsar/data apachepulsar/pulsar:3.1.0 bin/pulsar standalone

[Samreay]

Ah, I saw this issue #14298 asking for PULSAR_LOG_LEVEL and assumed that the issue being open meant that the env variable wasn't yet implemented. TIL. Thanks mate!

[jak78]

I'm happy your problem is solved. In my understanding, issue #14298 is about changing the log configuration at runtime without restarting the broker. This is still to be implemented.