Document URL: https://docs.openshift.com/container-platform/4.1/logging/efk-logging-eventrouter.html Section Number and Name: Deploying and Configuring the Event Router Describe the issue: 1) In 4.x, the logging stack will not process the eventrouter data unless MERGE_JSON_LOG=true - the efk-logging-eventrouter doc should explain this and provide a link to https://docs.openshift.com/container-platform/4.1/logging/config/efk-logging-fluentd.html#efk-logging-fluentd-json_efk-logging-fluentd 2) The Deployment name should be "logging-eventrouter" instead of "cluster-logging-eventrouter" - the fluentd config expects the pod name to begin with "logging-eventrouter" - otherwise, the log records will not be assigned a UID matching the source UID of the event, they will be assigned a random UID Suggestions for improvement: Additional information:
https://github.com/openshift/openshift-docs/pull/17040
Item #1: https://github.com/openshift/openshift-docs/pull/17040 [WIP] Item #2: https://github.com/openshift/openshift-docs/pull/17052
Issue #1 (the logging stack will not process the eventrouter data unless MERGE_JSON_LOG=true) being tracked via https://bugzilla.redhat.com/show_bug.cgi?id=1760511
Changes are live: https://docs.openshift.com/container-platform/4.1/logging/efk-logging-eventrouter.html#efk-logging-eventrouter-deploy_efk-logging-curator