Logs not showing up with SAM local - async issue? about lambda-monitoring HOT 3 CLOSED

Just thought I would give an update here incase anyone else sees this.

I was able to successfully use aws-lambda-java-log4j2 with version 1.1.0 from amazon. I then used the log4j-slf4j-impl library so that log4j2 is only used as the logging framework for slf4j. This allowed me to use SLF4J api in my libraries and libraries from others that depend on the SLF4J API while having logs route through the recommended and provided AWS logging framework.

Upon doing this, all of my logs are now back in the correct execution order with where the process was at during execution of the Lambda and it is working with SAM local the same it does on AWS lambda.

I'm not sure what the logback appender is doing in what I referenced above as to why it does not appear to be immediately flushing to the output stream for stdout - this is not an issue with SLF4J but with logback as the logging framework and the appender being used it would appear.

from lambda-monitoring.

Thanks for the detailed report - that's a really interesting finding. We're not doing anything particularly wild with logback, so it's definitely unexpected.

I do think it's worth trying to call out to LambdaLogger directly - if you'd like to take a swing at a PR for a new appender I'm happy to review it.

from lambda-monitoring.

@rmmeans - try this again with version 1.0.3 (just released, may take a few hours to hit Maven Central). The lack of a trailing newline was causing some havoc, both in test output and in CloudWatch logs.

from lambda-monitoring.