Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1792051

Summary: Fluentd cannot correctly handle newline (\n) character in the log content, which causes one log to be split into multiple logs
Product: OpenShift Container Platform Reporter: Zhigang Wang <zhigwang>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED DUPLICATE QA Contact: Anping Li <anli>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, xtian
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-17 20:00:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot 1
none
screenshot 2
none
loging-fluentd-cm.yaml
none
logging-fluentd-ds.yaml none

Description Zhigang Wang 2020-01-16 22:36:37 UTC
Created attachment 1652893 [details]
screenshot 1

Description of problem:

Fluentd collects log files. When it processing files, it cannot correctly handle newline (\n) character in the log content, which causes one log to be split into multiple logs.

After installing openshift, we adjusted the cluster-integrated EFK.
Disabled the elasticsearch and kibana components, changed the configuration of fluentd, and made the container logs collected by fluentd in the platform and pushed to the external kafka cluster, and then pushed by kafka to the external elasticsearch cluster.

When querying the log through external kibana, we found that only the first line of the java exception log can be viewed.

We learned that both logstash and fluentd can solve the problem of line breaks character by installing plugins.
I want to inquire whether the RedHat officialy support of openshift fluentd to the install these kind of plugins.
How do we solve these problem, does your company have product support of this problem?

Version-Release number of selected component (if applicable):

3.11.153

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Customer has checked these two bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1422008 and
https://bugzilla.redhat.com/show_bug.cgi?id=1573680

But saying that the issue still exists and they have 3.11.153 installed.

Comment 1 Zhigang Wang 2020-01-16 22:39:07 UTC
Created attachment 1652895 [details]
screenshot 2

Comment 2 Zhigang Wang 2020-01-16 22:40:13 UTC
Created attachment 1652896 [details]
loging-fluentd-cm.yaml

Comment 3 Zhigang Wang 2020-01-16 22:41:12 UTC
Created attachment 1652897 [details]
logging-fluentd-ds.yaml

Comment 4 Zhigang Wang 2020-01-16 22:41:52 UTC
Please let us know if you need more information from the customer

Comment 5 Jeff Cantrill 2020-01-17 20:00:48 UTC
Closing as duplicate.  Looking at the attached fluent conf, it does not include the content of https://github.com/openshift/origin-aggregated-logging/pull/1723/files#diff-9b277ce5ee2d1f49a653a614fcba17d9R1 which was added to specifically handle cases as describe.

*** This bug has been marked as a duplicate of bug 1740263 ***