Closed crosbymichael closed 10 years ago
Looking through skynet I see you have a syslog logger with a nice interface.
https://github.com/skynetservices/skynet/blob/master/log/log.go
The skynet logger is really nice. we can add that if you like it. I plan on doing a lot of cleanup in Skynet proper soon. One of the things we can do is move that into a shared package and use here.
At least being able to quieten all those "Updated Service TTL:" messages would be appreciated...
Oh, forget what I said... those messages apparently come from the skydns image:-/ I just wish docker had better logging (preferably with journald support).
[ Quoting notifications@github.com in "Re: [skydns] Improve logging suppor..." ]
At least being able to quieten all those "Updated Service TTL:" messages would be appreciated...
We currently rewriting skydns to use etcd as a backend, then these messages will automatically disappear.
/Miek
Miek Gieben
Also skydns2 uses the code from etcd to do the logging.
Right now there are many hard coded
log.X
calls throughout the code base. With a lot of volume this can really add a lot of output to the log files. I'm opening this so that we can discuss options.Currently the Go log pkg is not very way or open to extension.
log.Logger
is a struct, not an interface, and people usually consume the log pkg with the pkg func calls and not use the logger. It is hard to extend.Are few options that I can think of are:
I think having log levels is a good idea for this project. I would also like to find a good replacement for the log pkg that is not golog ( it's super complex ).
Ideas?