-
-
Notifications
You must be signed in to change notification settings - Fork 315
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
How to change the log level #494
Comments
Updating to v0.11.2 does not help |
Problem seems to be uber.zap. NewProduction is by default INFO, NewDevelopment is by default DEBUG. You should use BasicConfiguration, I guess. https://pkg.go.dev/go.uber.org/zap#hdr-Choosing_a_Logger Plus a new configuration parameter like log_level linked to the BasicConfiguration of uber.zap |
Hello, Basically, the reason is that currently, Caddy doesn't support defining global error level - the configuration file needs to be modified manually. The good news is that the new version of Caddy which is in a beta already has it: caddyserver/caddy#4028 Thanks! |
Caddy's new version (2.4.0) was released, you can now define the global default logging option:
This issue might be closed now. Thanks! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@dunglas the latest Mercure release (0.12.0) is still based on pre-2.4.0 Caddy. Do you think it might be updated at some point? |
Yes it will when I'll tag a new version. In the meantime you can build from sources using |
Is the log level still in the global section?? Since it doesn't seem like it.. Please document this better on your official docs site. |
Hello!
I try to change the log level of the mercure server (I'm using docker dunglas/mercure:v0.11.1). Can not find any solutions:
log {
level WARN
}
Howevery, all log msg are still displayed. Debug and Info too.
What can I do?
Best regards
Sommer
The text was updated successfully, but these errors were encountered: