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
Would it make sense to introduce configurable log levels to prevent logs from being flooded with debug messages? While I understand that debug messages are essential for development, they can be unnecessary and even distracting in production environments.
I noticed that there are DEBUG and NOTICE log messages, but currently, there doesn’t seem to be a way to filter them dynamically. It would be beneficial to have a configurable log level setting that allows users to suppress DEBUG messages (or other levels) as needed.
Suggested Improvement
• Implement a configurable log level setting that enables users to control the verbosity of logs.
• Provide an option to exclude DEBUG messages in production while keeping higher-priority logs like NOTICE, WARNING, or ERROR.
The text was updated successfully, but these errors were encountered:
Would it make sense to introduce configurable log levels to prevent logs from being flooded with debug messages? While I understand that debug messages are essential for development, they can be unnecessary and even distracting in production environments.
I noticed that there are
DEBUG
andNOTICE
log messages, but currently, there doesn’t seem to be a way to filter them dynamically. It would be beneficial to have a configurable log level setting that allows users to suppressDEBUG
messages (or other levels) as needed.Suggested Improvement
• Implement a configurable log level setting that enables users to control the verbosity of logs.
• Provide an option to exclude
DEBUG
messages in production while keeping higher-priority logs likeNOTICE
,WARNING
, orERROR
.The text was updated successfully, but these errors were encountered: