Logstash S3 output plugin, how do we get logging?

Elastic Stack Logstash
1

When I use the file output plugin I see INFO log lines that we are opening and closing a file to write to.

But when using the s3 output plugin I get writes but no logging.

log4j2.properties

status = debug
name = LogstashRspecConfig

appender.console.type = Console
appender.console.name = console
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = [%d{ISO8601}][%-5p][%-25c] %m%n

rootLogger.level = debug 
rootLogger.appenderRef.console.ref = console
2

Correct. The output does not log informational messages.

3

It looks like it at least used to provide some logging Uploader can't keep up · Issue #120 · logstash-plugins/logstash-output-s3 · GitHub

4

Indeed the output does have some DEBUG messages, but I do not see any INFO messages.

5

Debug messages as referenced aren't appearing with the provided log4j configuration. The question is how do we get logging output.

6

Well you could set --log.level to DEBUG, but that affects everything. When I configure an s3 input and call

curl -XGET 'localhost:9600/_node/logging?pretty'

then "logstash.inputs.s3" : "INFO", is in the list so you could try

curl -XPUT 'localhost:9600/_node/logging?pretty' -H 'Content-Type: application/json' -d'{ "logstash.inputs.s3" : "DEBUG" }'

You could also try appending

logger.randomname.name = logstash.inputs.s3
logger.randomname.level = DEBUG

to your log4j2.properties but I am not sure on that one.

7

I will try the CLI flag and take a look. Think there must be something wrong with the log4j2 config if messages are supposed to exist.

8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.