Aaron Lehmann bb8b9a6040 networkdb: Properly format memberlist logs ... Right now, items logged by memberlist end up as a complete log line embedded inside another log line, like the following: Nov 22 16:34:16 hostname dockerd: time="2016-11-22T16:34:16.802103258-08:00" level=info msg="2016/11/22 16:34:16 [INFO] memberlist: Marking xyz-1d1ec2dfa053 as failed, suspect timeout reached\n" This has two time and date stamps, and an escaped newline inside the "msg" field of the outer log message. To fix this, define a custom logger that only prints the message itself. Capture this message in logWriter, strip off the log level (added directly by memberlist), and route to the appropriate logrus method. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2016-12-01 19:08:07 -08:00
..
broadcast.go	Recover from transient gossip failures	2016-09-19 15:58:14 -07:00
cluster.go	networkdb: Properly format memberlist logs	2016-12-01 19:08:07 -08:00
delegate.go	Use monotonic clock for reaping networkDB entries	2016-10-19 22:30:47 -07:00
event_delegate.go	Reap failed nodes after 24 hours	2016-10-20 11:24:04 -07:00
message.go	Use protobuf in networkdb core messages	2016-05-17 09:18:24 -07:00
networkdb.go	Separate service LB & SD from network plumbing	2016-11-17 13:09:14 -08:00
networkdb.pb.go	Recover from transient gossip failures	2016-09-19 15:58:14 -07:00
networkdb.proto	Recover from transient gossip failures	2016-09-19 15:58:14 -07:00
networkdb_test.go	Add network scoped gossip database	2016-04-08 12:58:09 -07:00
watch.go	Add network scoped gossip database	2016-04-08 12:58:09 -07:00