Back to bug 1632895
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Noriko Hosoi | 2018-09-25 19:00:27 UTC | Summary | logging-eventrouter event not formatted correctly in Elasticsearch when using MUX | [3.11] logging-eventrouter event not formatted correctly in Elasticsearch when using MUX |
| Noriko Hosoi | 2018-09-25 19:01:18 UTC | Status | NEW | ASSIGNED |
| Noriko Hosoi | 2018-09-28 15:55:36 UTC | Status | ASSIGNED | POST |
| 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:45:05 UTC | Status | POST | MODIFIED |
| CC | jcantril | |||
| errata-xmlrpc | 2018-11-01 18:12:32 UTC | Status | MODIFIED | ON_QA |
| Qiaoling Tang | 2018-11-02 09:31:00 UTC | Status | ON_QA | VERIFIED |
| CC | qitang | |||
| errata-xmlrpc | 2018-11-19 12:56:29 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2018-11-20 03:10:43 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2018-11-19 22:10:43 UTC | |||
| errata-xmlrpc | 2018-11-20 03:11:20 UTC | Link ID | Red Hat Product Errata RHBA-2018:3537 |
Back to bug 1632895