{"push_id":999135869,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"624bdd8f143d813cd215e0be8781618cd88ea862","before":"3a853efe699438dd87f418a3943a68a4744b3a1c","commits":[{"sha":"624bdd8f143d813cd215e0be8781618cd88ea862","author":{"email":"c5ead667a69b1a48cae093a60913848e634022b0@gmail.com","name":"Solganik Alexander"},"message":"Fixes #18712. Add rfc5424 log format for syslog.\n\nPreviously docker used obsolete rfc3164 syslog format for syslog. rfc3164 explicitly\nuses semicolon as a separator between 'TAG' and 'Content' section of the log message.\nDocker uses semicolon as a separator between image name and version tag.\nWhen {{.ImageName}} was used as a tag expression and contained \":\" syslog parser mistreated\n\"tag\" part of the image name as syslog message body, which resulted in incorrect \"syslogtag\" been reported by syslog\ndaemon.\nUse of rfc5424 log format partually fixes the issue as it does not use semicolon as a separator.\nHowever using default rfc5424 syslog format itroduces backward incompatability because rsyslog template keyword  %syslogtag%\nis parsed differently. In rfc3164 it uses the \"TAG\" part reported before the \"pid\" part. In rfc5424 it uses \"appname\" part reported\nbefore the pid part, while tag part is introduced by %msgid% part.\nFor more information on rsyslog configuration properties see: http://www.rsyslog.com/doc/master/configuration/properties.html\n\nNew Option to configure syslog on docker is added, user can now specify --log-opt syslog-format=rfc5424 in order to use syslog rfc5424 format\nDefault behaviour is not changed, keeping default syslog format in order to keep backwards compatability.\n\nSigned-off-by: Solganik Alexander <solganik@gmail.com>","distinct":true,"url":"https://api.github.com/repos/solganik/docker/commits/624bdd8f143d813cd215e0be8781618cd88ea862"}]}