splunk-connect-for-kubernetes: Events not flushing until next event occurs because of multine code block

What happened: whenever event logged in pod it is not reflecting immediately in splunk UI until and unless another event get generated the old event will get updated with new event timestamp as splunk timestamp.

What you expected to happen: Whenever new event logged in pod it should reflect in splunkUI with realtime.

How to reproduce it (as minimally and precisely as possible):Deploy splunk Connect Kubernetes using manifest files and pod to reflect logs to splunk.

Anything else we need to know?:The pod logtime and splunk time should be similar in this case the old event logged with new event timestamp.

Environment:

• Kubernetes version (use kubectl version): Client Version: version.Info{Major:“1”, Minor:“17”, GitVersion:“v1.17.0”, GitCommit:“70132b0f130acc0bed193d9ba59dd186f0e634cf”, GitTreeState:“clean”, BuildDate:“2019-12-07T21:20:10Z”, GoVersion:“go1.13.4”, Compiler:“gc”, Platform:“linux/amd64”} Server Version: version.Info{Major:“1”, Minor:“13+”, GitVersion:“v1.13.12-gke.13”, GitCommit:“39fe6cf6b77a3a0f620bd89db92f5133be67aa91”, GitTreeState:“clean”, BuildDate:“2019-11-13T20:44:51Z”, GoVersion:“go1.12.11b4”, Compiler:“gc”, Platform:“linux/amd64”}

• Ruby version (use ruby --version):

• OS (e.g: cat /etc/os-release): NAME=“CentOS Linux” VERSION=“7 (Core)” ID=“centos” ID_LIKE=“rhel fedora” VERSION_ID=“7” PRETTY_NAME=“CentOS Linux 7 (Core)” ANSI_COLOR=“0;31” CPE_NAME=“cpe:/o:centos:centos:7” HOME_URL=“https://www.centos.org/” BUG_REPORT_URL=“https://bugs.centos.org/”

CENTOS_MANTISBT_PROJECT=“CentOS-7” CENTOS_MANTISBT_PROJECT_VERSION=“7” REDHAT_SUPPORT_PRODUCT=“centos” REDHAT_SUPPORT_PRODUCT_VERSION=“7”

• Splunk version:splunk-connect-Kubernetes-1.13
• Others:Gke-1.12