Back to bug 1554293

Who When What Removed Added
Jeff Cantrill 2018-03-12 12:59:06 UTC Summary logging-eventrouter json log is't filter well logging-eventrouter event not formatted correctly in Elasticsearch when using crio
Jessica Forrester 2018-03-12 15:12:59 UTC Target Release 3.9.0 3.9.z
CC jforrest
Jeff Cantrill 2018-03-13 14:06:18 UTC Status NEW ASSIGNED
Assignee jcantril jwozniak
Jan Wozniak 2018-03-13 15:06:38 UTC Summary logging-eventrouter event not formatted correctly in Elasticsearch when using crio logging-eventrouter event not formatted correctly in Elasticsearch when using crio and MUX
Jan Wozniak 2018-03-15 14:54:11 UTC Summary logging-eventrouter event not formatted correctly in Elasticsearch when using crio and MUX logging-eventrouter event not formatted correctly in Elasticsearch when using MUX
Jan Wozniak 2018-03-29 15:06:52 UTC Flags needinfo?(rmeggins)
Rich Megginson 2018-03-29 16:31:36 UTC Flags needinfo?(rmeggins)
Peter Portante 2018-05-21 14:34:19 UTC CC pportant
Noriko Hosoi 2018-05-31 21:58:46 UTC CC nhosoi
PnT Account Manager 2018-07-31 21:53:15 UTC Assignee jwozniak jcantril
Noriko Hosoi 2018-08-02 18:51:05 UTC Status ASSIGNED ON_QA
Jeff Cantrill 2018-08-06 13:05:03 UTC Assignee jcantril nhosoi
Anping Li 2018-09-19 10:05:44 UTC Status ON_QA ASSIGNED
Noriko Hosoi 2018-09-19 18:37:37 UTC CC anli
Flags needinfo?(anli)
Noriko Hosoi 2018-09-19 22:56:30 UTC Flags needinfo?(anli)
Noriko Hosoi 2018-09-25 18:55:51 UTC Blocks 1632892
Noriko Hosoi 2018-09-25 18:58:10 UTC Blocks 1632895
Noriko Hosoi 2018-09-25 19:01:01 UTC Summary logging-eventrouter event not formatted correctly in Elasticsearch when using MUX [3.9] logging-eventrouter event not formatted correctly in Elasticsearch when using MUX
Noriko Hosoi 2018-09-28 15:44:31 UTC Status ASSIGNED POST
Noriko Hosoi 2018-09-28 15:53:52 UTC Doc Text Cause:
When fluentd is configured as the combination of collectors and MUX, event logs from the event were supposed to be processed by MUX not by the collector for the both MUX_CLIENT_MODE maximal and minimal. It is because if an event log is formatted in the collector (note: the event record is put under the kubernetes key), the log is forwarded to MUX and passed to the k8s-meta plugin there and the existing kubernetes record is overwritten. It wiped out the event info from the log.

Fix 1:
To avoid the replacement, if the log is from event router, the tag is rewritten to ${tag}.raw in input-post-forward-mux.conf, which makes the log treated in the MUX_CLIENT_MODE=minimal way.

Fix 2:
There was another bug in ansible. That is, the environment variable TRANSFORM_EVENTS was not set in MUX even if openshift_logging_install_eventrouter is set to true.

Result:
With these 2 fixes, the event logs are correctly logged when MUX is configured with MUX_CLIENT_MODE=maximal as well as minimal.
Doc Type If docs needed, set a value Bug Fix
Jeff Cantrill 2018-10-19 20:43:39 UTC Status POST MODIFIED
CC jcantril
errata-xmlrpc 2018-11-27 17:39:48 UTC Status MODIFIED ON_QA
Joel Davis 2018-11-27 18:54:12 UTC Status ON_QA MODIFIED
errata-xmlrpc 2018-11-27 18:57:48 UTC Status MODIFIED ON_QA
Anping Li 2018-11-29 09:59:40 UTC Status ON_QA VERIFIED
errata-xmlrpc 2018-12-11 00:01:32 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2018-12-13 19:26:59 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2018-12-13 19:26:59 UTC
errata-xmlrpc 2018-12-13 19:27:11 UTC Link ID Red Hat Product Errata RHBA-2018:3748

Back to bug 1554293