You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now when printing log items, the log level (DEBUG, INFO, WARN, ERROR) is correctly state in the structured log JSON, but in cloudwatch they are processed all as INFO logs.
Expected Behavior
Each log item in CloudWatch is processed using the correct logging level.
Current Behavior
All log items have an INFO log level in CW.
Possible Solution
Use the proper console method (console.debug, console.info, console.warn, console.error).
Steps to Reproduce
N/A
Environment
Powertools version used: main branch
Packaging format (Layers, npm): NPM
AWS Lambda function runtime: all
Debugging logs: N/A
Related issues, RFCs
N/A
The text was updated successfully, but these errors were encountered:
dreamorosi
added
logger
This item relates to the Logger Utility
and removed
triage
This item has not been triaged by a maintainer, please wait
labels
Jan 3, 2022
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
dreamorosi
changed the title
Logger: bug - incorrect log level in CloudWatch
Bug: incorrect log level in CloudWatch
Nov 14, 2022
Bug description
Right now when printing log items, the log level (DEBUG, INFO, WARN, ERROR) is correctly state in the structured log JSON, but in cloudwatch they are processed all as INFO logs.
Expected Behavior
Each log item in CloudWatch is processed using the correct logging level.
Current Behavior
All log items have an INFO log level in CW.
Possible Solution
Use the proper console method (console.debug, console.info, console.warn, console.error).
Steps to Reproduce
N/A
Environment
Related issues, RFCs
N/A
The text was updated successfully, but these errors were encountered: