groob
commented
8 years ago IMO, go-kit represents the state of the art in Go logging libraries.
- unlike most loggers, it's an interface, not a concrete type
- it enforcers structured logging
- supports context
- provides a nice wrapper for the stdlib logger
- supports concurrent logging with SyncLogger
- includes a logger func type, which I believe could give us the ability to do some of the same things as the Logrus hooks
The talk by Chris Hines on the design of the logger is worth checking out as well.
regarding configurable outputs, this thread has a good explanation with code samples of how to achieve different log destinations.
Having said that, kit/log is opinionated about certain things, like this
Right now we use logrus for application logs and these can only be logged to stdout. We also use lumberjack for osquery result and status logs and these can only be logged to rotating files.
Logrus has an internesting hooks API and go-kit also has an interesting logging library.
It would be nice if all logs (osquery result logs, osquery status logs, kolide application logs, kolide alert logs, etc) could be picked and mixed and matched. For example, I might want to send one set of logs to ES, one set of logs to Kafka, one set of logs to a local rotating file and one set of logs to a syslog server. It would be nice if the kolide binary supported this level of configuration natively. Ideally, this would all happen with the same library as well.