sending the logs through journald involves a LOT of wasted effort
writing the logs to disk and then reading them from disk wastes a fair amount of disk I/O (and you have the hassle of managing space)
it looks like using the stock docker syslog log-driver leaves out a huge amount of needed metadata (like what container the log is being generated in)
are people really just having the logs go to disk or to the journal? I see references to people using other advanced tools with docker/kubernetes logs, but no mention of how they are getting there?
_______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
