Feature request: Log warning message if Advanced Logging Controls log level is less verbose than Logger level

[tknisch]

Use case

If I use the Logger for example at Debug level and the Advanced Logging Controls are set to Info I will not get the log messages printed.
It would be nice, the a warning message could be printed if this constellation is given.

Solution/User Experience

Print a warning message (configurable) if log messages would be suppressed by Advanced Logging Controls.

Alternative solutions

Acknowledgment

• This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[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 #typescript channel on our Powertools for AWS Lambda Discord: Invite link

[dreamorosi]

Hi @tknisch, thank you for opening this issue.

As we discussed on Discord, I think this is something we missed and should address.

We already have a way to detect whether Advanced Logging Controls is enabled and its level, so I think with some light refactoring we should be able to check that value and emit a warning if the log level is less verbose and log buffering is enabled.

We should also add a callout to the docs as additional measure.

Thank you for bringing this up!

[dreamorosi]

I've added the help-wanted label, so if anyone is interested in contributing please leave a comment and I'll assign the issue to you.

In terms of implementation, I think we should add some logic around here and call this.getEnvVarsService().getAwsLogLevel();. If the value of that variable is less verbose than the log buffering threshold, then we should call this.warnOnce() and let the customer know.

[ConnorKirk]

I can take a look