-
Notifications
You must be signed in to change notification settings - Fork 189
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
Remove dependency to github.com/brutella/log #20
Comments
Hi, Dave Cheney has some interesting ideas: http://dave.cheney.net/2015/11/05/lets-talk-about-logging Kinda like it :-) /michael |
regardless of how logging is done, is there a way to suppress VERB when using hc ? I have tried importing brutella/logs and setting |
@brutella thanks but this does not work for me, if I take your example above and set log.Verbose and log.Info to false I still see both debug levels:
|
Log messages are reduced to debug and info log messages. Info log messages are useful information to the user. Debug log messages are used for debugging purposes. Errors messages are now info log messages followed by a panic call. By default debug logs are sent to /dev/null. You can enable debug logs by calling log.Debug.Enable() once. #20
There are now 2 log levels: info and debug. Info messages are messages for the user. Debug messages are messages for the developer. You can enable the debug log level like this: import "github.com/brutella/hc/log"
log.Debug.Enable() |
This works great, thank you Matthias! |
@eaigner What would be a better way to implement log levels?
The text was updated successfully, but these errors were encountered: