-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add Notice level #121
Comments
This is a pretty narrow use case, and not something that's come up before. It won't be added to Logrus for now. Thanks for the suggestion! |
I would also like to see this Log level be introduced into |
@kellydunn it's planned for 1.x that you can add any logging levels you want, as levels will simply become fields, and formatters will support that field or they won't. |
@sirupsen: is more information about 1.x available somewhere? |
@jonhoo not yet, I'm still thinking about it. But it'll be much more customizable, msg, levels etc. won't be special, and center around Go contexts (see the package). |
@sirupsen sounds great. Being able to have multiple debug levels, and being able to use the logging library sensibly in two different packages that are both used simultaneously, are two of my biggest concerns atm. |
+1 for customizable log levels. A generic
Personally, I prefer the # 2. |
Did this ever happen and land in master? |
It would be nice to have an additional level between Info and Warning
Notice
. I tend to use logging as follows:Notice
: System start/stop, significant-but-normal eventsInfo
: Detail: User connected, transaction applied etc.Debug
: In depth debugging/tracing, e.g. packet dumpsI usually would have the default log level set to Notice and have Errors, Fatal and Panic logged to a remote server for analysis.
The text was updated successfully, but these errors were encountered: