Unable to get stack trace logging to work about lambda-monitoring HOT 3 CLOSED

Please take a look at #4 (comment)

Maybe this will help.

from lambda-monitoring.

from lambda-monitoring.

I figured out what is wrong when running outside of AWS. The default layout uses \r as line separator so that it plays well with CloudWatch. Outside of AWS, this causes the cursor to keep going back to the beginning of the line (clearing what's been written so far) upon encountering \r. As a result, the only line that gets shown in the terminal is the last one. I resolved the issue by using a different dependency for my local tests:

<dependency>
    <groupId>io.symphonia</groupId>
    <artifactId>lambda-logging</artifactId>
    <classifier>no-config</classifier>
    <scope>test</scope>
</dependency>

Combined with a layout in src/test/resources/logback.xml that does not use \r:

<pattern>[%d{yyyy-MM-dd HH:mm:ss.SSS}] %X{AWSRequestId:-NO_REQUEST_ID} %highlight(%.-6level) %logger{5} - %msg%nopex%n%highlight(%rEx)</pattern>

The DEFAULT_PATTERN from symphonia (for reference)

"[%d{yyyy-MM-dd HH:mm:ss.SSS}] %X{AWSRequestId:-" + NO_REQUEST_ID + "} %.-6level %logger{5} - %msg \r%replace(%ex){'\n','\r'}%nopex%n";

I've added extra bells and whistles for my local tests version (highlighting, stack traces always start on the line following the log entry, with root cause first).

from lambda-monitoring.