From f8965a6f41d20029e0209873012e4309f93e60c0 Mon Sep 17 00:00:00 2001 From: Alex Robinson Date: Fri, 26 Feb 2016 22:58:46 +0000 Subject: [PATCH] Fix parsing of kube logs to handle logs split across lines. I didn't expect glog to split single log statements onto multiple lines, but apparently it does if they're long enough. This groups them back together appropriately. --- .../fluentd-es-image/td-agent.conf | 20 +++++++++++++++---- .../fluentd-gcp-image/google-fluentd.conf | 20 +++++++++++++++---- 2 files changed, 32 insertions(+), 8 deletions(-) diff --git a/cluster/addons/fluentd-elasticsearch/fluentd-es-image/td-agent.conf b/cluster/addons/fluentd-elasticsearch/fluentd-es-image/td-agent.conf index d76522680aa..269f0abeb75 100644 --- a/cluster/addons/fluentd-elasticsearch/fluentd-es-image/td-agent.conf +++ b/cluster/addons/fluentd-elasticsearch/fluentd-es-image/td-agent.conf @@ -162,11 +162,17 @@ tag etcd +# Multi-line parsing is required for all the kube logs because very large log +# statements, such as those that include entire object bodies, get split into +# multiple lines by glog. + # Example: # I0204 07:32:30.020537 3368 server.go:1048] POST /stats/container/: (13.972191ms) 200 [[Go-http-client/1.1] 10.244.1.3:40537] type tail - format /^(?\w)(?