Bug 1740263 - enable the parsing of docker log-driver=json-file continuation lines using fluent concat plugin
Summary: enable the parsing of docker log-driver=json-file continuation lines using fl...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.11.z
Assignee: Rich Megginson
QA Contact: Anping Li
URL:
Whiteboard:
: 1792051 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-12 14:29 UTC by David Caldwell
Modified: 2023-03-24 15:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Fluentd did not look for continuation log lines from the docker json-file or journald log driver. Consequence: Very long log lines were split in Elasticsearch and Kibana. Fix: Change Fluentd to look for continuation log lines and reconstruct them before sending to Elasticsearch. We used a Fluentd plugin called fluent-plugin-concat to do this. We had to backport the 2.4.0 version to Fluentd 0.12.43 in order to work with OCP 3.11. Result: Very long log lines are not split in Elasticsearch. The entire log can be viewed in Kibana.
Clone Of:
Environment:
Last Closed: 2019-09-03 15:56:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 1723 0 'None' closed Bug 1740263: enable the parsing of docker log-driver=json-file continuation lines using fluent concat plugin 2021-01-11 08:45:53 UTC
Red Hat Product Errata RHBA-2019:2580 0 None None None 2019-09-03 15:56:11 UTC

Comment 1 Rich Megginson 2019-08-14 15:15:34 UTC 
https://github.com/openshift/origin-aggregated-logging/pull/1723
Comment 5 Anping Li 2019-08-29 07:18:55 UTC 
Verified in 3.11.141.
USE_MULTILINE_JSON - default false - if set to true, and you are using docker with --log-driver=json-file (which is the default), Fluentd will reconstruct whole log records from the docker log partial fragments
Comment 7 errata-xmlrpc 2019-09-03 15:56:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2580
Comment 10 Jeff Cantrill 2020-01-17 20:00:48 UTC 
*** Bug 1792051 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.