As noted at #132770 we currently drop all log message emitted by dependencies which use SLF4J for their logging:
[WARN ][stderr ] [es] SLF4J: No SLF4J providers were found.
[WARN ][stderr ] [es] SLF4J: Defaulting to no-operation (NOP) logger implementation
[WARN ][stderr ] [es] SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
This includes various SDKs including the AWS SDK and makes troubleshooting problems in these SDKs very difficult. We need to find a way to route SLF4J log messages into the Elasticsearch server logs.
We must also replace all the existing usages of slf4j-nop with a proper logger rather than just silently dropping these log messages.
Relates ES-12645
As noted at #132770 we currently drop all log message emitted by dependencies which use SLF4J for their logging:
This includes various SDKs including the AWS SDK and makes troubleshooting problems in these SDKs very difficult. We need to find a way to route SLF4J log messages into the Elasticsearch server logs.
We must also replace all the existing usages of
slf4j-nopwith a proper logger rather than just silently dropping these log messages.Relates ES-12645