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

One of the errors dispatched by the [oauth2 library](https://github.com/golang/oauth2/blob/master/internal/token.go#L256) contains a `http.Response` which causes the following error: error logging: json: unsupported type: func() (io.ReadCloser, error) This feels like something `WithError(err)`...

This would require some updates, but it would help for handlers like papertrail and ES to have the ability to buffer, with a `defer log.Flush()`. For ones that go to...

If you are unmarshaling from JSON you can just pass it to the handler, but if you don't have direct access to the handler we need another method for that.

enhancement

This way, it's possible to do things like this: ```go trace := log.Trace("test") ret, err := handler() if err != nil { trace = trace.WithFields(...custom fields just in case of...

This handler will report to LogEntries with a [TCP token](https://github.com/bsphere/le_go#usage).

It would be nice to have an optional ``WithLazyFields(key string, func() interface{})`` method to calculate field value only when it's retrieved with ``Get(key string)`` method. I.e. some entries may be...

Set a reasonable default and then grow accordingly, instead of defaulting to a pretty large offset which looks kind of silly in simpler cases.

handlers

No need to rewrite all that stuff

handlers

Hi, i'm using apex in a few projects and would like to know if it is still maintained? Last changes are 3 years ago...