@Logging annotation with logEvent = true does not play nice with @Tracing annotation in RequestStreamHandler about powertools-lambda-java HOT 6 CLOSED

Hi, @allenada Thanks for opening an issue with detailed information. I will have a look at it sometime this week.

from powertools-lambda-java.

I did have some time to take a deeper look into this myself. Looks like if you change LambdaLoggingAspect.java#L78 to the following then the issue is resolved (at least in my local unit test):

@Around(value = "callAt(logging) && execution(@software.amazon.lambda.powertools.logging.Logging* *.*(InputStream, ..))", argNames = "pjp,logging")

from powertools-lambda-java.

I did managed to replicate the issue and also understand the problem, which exists only if you are using input stream version of handler together with tracing and logging together.

I haven't find a proper solution yet, but I will check the solution which you mentioned as well and also dive a bit more deeper this week.

In the meantime(while we fix this) I am sure there must be reasons on using stream handler version, but if it helps, you may also switch the lambda function handler to the request handler implementation.

from powertools-lambda-java.

I am planning to revisit this issue sometime this week.

from powertools-lambda-java.

@allenada This should be fixed with #567

from powertools-lambda-java.

Release as part of https://github.com/awslabs/aws-lambda-powertools-java/releases/tag/v1.8.0 @allenada

from powertools-lambda-java.