Bug 1588828 - After upgrade to 3.6 some logs are not showing in the Kibana webUI
Summary: After upgrade to 3.6 some logs are not showing in the Kibana webUI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.9.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
: 3.9.z
Assignee: Rich Megginson
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1588772 1588827
Blocks: 1588829
TreeView+ depends on / blocked
 
Reported: 2018-06-07 22:49 UTC by Rich Megginson
Modified: 2021-12-10 16:19 UTC (History)
5 users (show)

Fixed In Version: logging-fluentd-container-v3.9.31-1
Doc Type: Bug Fix
Doc Text:
Cause: The incoming data has a field `record["event"]` that is a String value and not the Hash value expected by the transform_eventrouter code. Consequence: This causes the code to throw an error and fluentd to emit an error like this: ``` error_class=NoMethodError error="undefined method `key?' for \"request\":String" ``` Fix: The transform_eventrouter code has been changed to only process the `record["event"]` field if it is a Hash. Result: Records can flow through to Elasticsearch again.
Clone Of: 1588827
: 1588829 (view as bug list)
Environment:
Last Closed: 2018-08-09 22:13:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ViaQ fluent-plugin-viaq_data_model pull 13 0 None closed Bug 1588772 - After upgrade to 3.6 some logs are not showing in the K… 2020-06-20 01:09:48 UTC
Red Hat Product Errata RHBA-2018:2335 0 None None None 2018-08-09 22:14:41 UTC

Comment 2 Anping Li 2018-06-19 05:42:45 UTC
The fix is not in openshift3/logging-fluentd/images/v3.9.31-2.

Comment 4 Jeff Cantrill 2018-07-09 14:50:57 UTC
Moving to modified as the dependent RPM is in the compose.

Comment 6 Anping Li 2018-07-31 10:11:26 UTC
Works with logging-fluentd:v3.9.40

Comment 8 errata-xmlrpc 2018-08-09 22:13:49 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-2018:2335


Note You need to log in before you can comment on or make changes to this bug.