Structured logging as used in log15/logrus about kit HOT 5 CLOSED

@tonyhb I am a heavy user and one of the maintainers of log15, so I am familiar with the feature you linked to. Honestly, I've never felt the need to use that feature. I would like to hear more about your experience to get some perspective on the benefits of this feature.

from kit.

@ChrisHines for me it's only the structure and ease of readability of using map-like arguments instead of varargs — though that's about the only reason. It's why I'm a huge fan of Logrus' log.Fields{...}. Completely understand that personal preference isn't a valid reason for implementation, though.

from kit.

@tonyhb I am interested to see an example of how you use Logrus' log.Fields{...} or log15.Ctx.

One of the early proposals for the Go kit log API had a Logrus style API. I argued against that style here: #21 (comment).

from kit.

I do see the value in having typed arguments to Log, especially (perhaps only) for applications using log-structured data, rather than simple application logs. But I'd expect all of those use cases would have application-specific types, and they'd all boil down to wrappers around the existing API anyway, so I'm not sure how much value an explicit Fields type would provide.

from kit.

Closing this as out of scope for the core log package.

from kit.