The release notes do not mention it, but having upgraded to 6.3.0 logstash is now producing additional logging to stdout. This appears to me to be the effect of 9076. Looking at the new log4j2.properties there are a couple of console loggers that have been added, but I cannot figure out why that was done. Any ideas?
Sending Logstash's logs to /opt/applications/logstash/logs/loads which is now configured via log4j2.properties
[2018-06-14T14:17:50,453][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.queue", :path=>"/tmp/data/load.8141/queue"}
[2018-06-14T14:17:50,461][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.dead_letter_queue", :path=>"/tmp/data/load.8141/dead_letter_queue"}
[2018-06-14T14:17:50,760][WARN ][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified
[2018-06-14T14:17:50,774][INFO ][logstash.agent ] No persistent UUID file found. Generating new UUID {:uuid=>"2a8e4afe-f6df-418d-8d32-f01ac2f96977", :path=>"/tmp/data/load.8141/uuid"}
[2018-06-14T14:17:50,919][INFO ][logstash.runner ] Starting Logstash {"logstash.version"=>"6.3.0"}
[2018-06-14T14:17:52,749][INFO ][logstash.pipeline ] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>1, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50}
[2018-06-14T14:17:52,997][INFO ][logstash.pipeline ] Pipeline started successfully {:pipeline_id=>"main", :thread=>"#<Thread:0x721f2e2d@/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:245 run>"}
[2018-06-14T14:17:53,041][INFO ][logstash.agent ] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]}