Bug: Logger constructor ignores `level` argument after first call

[dennis-benchling]

Expected Behaviour

According to the docs, we should be able to set the log level explicitly through the level parameter to Logger.

Current Behaviour

The level parameter is properly set the first time you instantiate Logger, but subsequent instantiations with the same service name will not set the log level. (It will always be the original value from the first instance.)

Code snippet

from aws_lambda_powertools import Logger

first = Logger(level="INFO")
second = Logger(level="DEBUG")

print(f"first level = {first.log_level}") # first level = 20
print(f"second level = {second.log_level}") # second level = 20. (Should be 10)

Possible Solution

In Logger._init_logger, setLevel should be called before the early return.

Steps to Reproduce

Run the following code:

from aws_lambda_powertools import Logger

first = Logger(level="INFO")
second = Logger(level="DEBUG")

print(f"first level = {first.log_level}") # first level = 20
print(f"second level = {second.log_level}") # second level = 20. (Should be 10)

Powertools for AWS Lambda (Python) version

latest

AWS Lambda function runtime

3.8

Packaging format used

PyPi

Debugging logs

[boring-cyborg]

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

[anafalcao]

Hello @dennis-benchling !
Thank you so much for opening this issue. The Logger is designed to follow a singleton-like pattern for each unique service name. When you create multiple Logger instances with the same service name (and not defining a service name means it's service_undefined), they will reuse the same underlying logger instance, maintaining consistent log levels and configurations.
This behavior is intentional and documented, as it allows for seamless logging across different modules of your application without the need to pass logger instances explicitly.
For your use case, you could follow the example from setting_log_level_programmatically.py or assign a different service name for each Logger.
Let me know if it solves your question or if there's anything else we can help you with!

[leandrodamascena]

Hey @dennis-benchling! I'm closing this issue as "not a bug" and please reopen if you need.