Recommendation for Logging data in AWS Lambda

Question

AWS lambda currently supports two ways for logging, when Lambda function written in Java.

• log4j
• LambdaLogger

I want to know if is their any advantage of using one logging scheme over other.

Thanks!

Answer 1

What I understood from Aws Lambda Java Logging and searching around net is

• Log4J

  • pros: you can customize logs(using log4j.properties).
  • cons: it increase the size of your jar/zip as you add more dependency to your project

• LambdaLogger

  • pros: it saves memory as it is already embeded on your dependencies
  • cons: it can't be customizable

I hope that it helps!

Answer 2

In my opinion to keep it simple.

1. Assume you have an application project in maven where there will be multiple maven modules. You won't be passing context.getLogger() OR context argument every time you call some other module's implementation.

2. If you have a single handler function with no modules and multiple classes. In this case, you can start your AWS Lambda handler function code and get the context.getLogger() to get Lambda logger.

For more info : http://docs.aws.amazon.com/lambda/latest/dg/programming-model-v2.html