aws / aws-lambda-java-libs

The documentation on this page: https://docs.aws.amazon.com/lambda/latest/dg/java-logging.html#java-logging-advanced

If you don't assign a level to your log output, Lambda will automatically assign it the level INFO.

But this does not seem to be true. I am getting UNDEFINED in my tests, as this code seems to reinforce:

aws-lambda-java-libs/aws-lambda-java-core/src/main/java/com/amazonaws/services/lambda/runtime/logging/LogLevel.java

Lines 6 to 9 in 3d8dfb6

    
           public enum LogLevel { 
        
               // UNDEFINED log level is used when the legacy LambdaLogger::log(String) function is called 
        
               // where the loglevel is not defined. In this case we're not filtering the message in the runtime 
        
               UNDEFINED,

According to this code it seems like UNDEFINED is intended, so perhaps the docs should be updated.

Thanks.

this is fixed in versions 2.4.2 of RIC, which is already available in maven central. Managed runtime and OCI base images deployments are also scheduled

Closing the issue as the fix has been deployed recently. Feel free to reopen in case of further question

	public enum LogLevel {
	// UNDEFINED log level is used when the legacy LambdaLogger::log(String) function is called
	// where the loglevel is not defined. In this case we're not filtering the message in the runtime
	UNDEFINED,

AWS documentation says LambdaLogger will default to the INFO log level, but it is actually defaulting to UNDEFINED