feat: Powertools will now override the Log4J log level configured if the 'LOG_LEVEL' environment variable is set to a Log4J Level (INFO, ERROR etc...)

Author: msailes

src/main/java/software/amazon/lambda/logging/internal/LambdaLoggingAspect.java

@@ -11,9 +11,12 @@
 
 import com.amazonaws.services.lambda.runtime.Context;
 import com.fasterxml.jackson.databind.ObjectMapper;
+import org.apache.logging.log4j.Level;
 import org.apache.logging.log4j.LogManager;
 import org.apache.logging.log4j.Logger;
 import org.apache.logging.log4j.ThreadContext;
+import org.apache.logging.log4j.core.LoggerContext;
+import org.apache.logging.log4j.core.config.Configurator;
 import org.apache.logging.log4j.core.util.IOUtils;
 import org.aspectj.lang.ProceedingJoinPoint;
 import org.aspectj.lang.annotation.Around;
@@ -33,6 +36,15 @@
 @Aspect
 public final class LambdaLoggingAspect {
     private static final ObjectMapper mapper = new ObjectMapper();
+    private static final String LOG_LEVEL = System.getenv("LOG_LEVEL");
+
+    static {
+        if (LOG_LEVEL != null) {
+            LoggerContext ctx = (LoggerContext) LogManager.getContext(false);
+            Configurator.setAllLevels(LogManager.getRootLogger().getName(), Level.getLevel(LOG_LEVEL));
+            ctx.updateLoggers();
+        }
+    }
 
     @SuppressWarnings({"EmptyMethod", "unused"})
     @Pointcut("@annotation(powerToolsLogging)")