-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(web,server)!: runtime log level #5672
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is nice! I do think we should keep the option to configure log level early via an env var, I can imagine things breaking hard enough that you can't even make it into the UI to set the log level. A config file would work there, but is relatively quite a bit more work to set up and might interfere with other troubleshooting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job! Just some minor things... ;)
Also, I agree with Boet and I think we should actually keep the env variable for this
How should I resolve the two? Should I just ignore the runtime value while the environment variable is set? |
c1f6412
to
a14bdb7
Compare
36e658f
to
d154fdb
Compare
* feat: change log level at runtime * chore: open api * chore: prefer env over runtime * chore: remove default env value
Warning
Breaking Change
LOG_LEVEL
value ofsimple
has been removed.Use
log
instead (or remove the env entirely)Change the log level at runtime:
LOG_LEVEL
is set at the environment variable level.