log icon indicating copy to clipboard operation
log copied to clipboard

Structured logging package for Go.

Results 50 log issues
Sort by recently updated
recently updated
newest added

If users want to create a `log.Level` directly from an integer they need to wait for `log.SetLevel` to fail or write their own checks for whether a log level integer...

lots of systems still rely heavily on syslog, it'd be really good for there to be a syslog aware handler. some features I'd like to see in a hypothetical handler:...

handlers

This is my first pass at implementing this handler. I wrote a quick little test script which seems to produce the behaviour I expect, but I welcome feedback on it....

Primarily targeted at development mode, allow clients to configure a filter for what will get passed through. ```go log.SetHandler(log.FieldFilter("handler", "Login", json.New(os.Stderr))) ```

Any opinions on this? It's available from `runtime.Caller`. Following the current design, it could be enabled by having a function like `log.IncludeCaller(bool)` and then every entry would include a field...

https://github.com/apex/log/commit/89ce6f11b2dc2a7603f3429d7b3076c526980841 added the filename and line numbers of where a `pkg/errors` error stacktrace was taken if there was one attached. For me, it would be nice when doing local debugging...

logging is really a subset of tracing, and the opentracing API is pretty nice, certainly nothing to complain about. I think it would be great to have apex/log "2.0" effectively...

Hello! In the spirit of simplifying the logrus API, this PR replaces `*Entry` in the public interface to be `Interface`. Most of the changes were mechanical in nature (it just...

We experienced a crash today that I'm having trouble diagnosing. The error occurred when calling `logger.Info` inside a goroutine. There were several parallel tasks, all which log when they complete....

bug

hi, the method `LeveL.String` panics when `Level==InvalidLevel`. https://github.com/apex/log/blob/master/levels.go#L44 https://github.com/apex/log/blob/master/levels.go#L17 I suggest to add a statement before the slice access so that this pseudo value does not appear in the `levelNames`...