Red Hat Bugzilla – Bug 1324996
JSON message fields are getting overwritten
Last modified: 2018-07-18 21:38:35 EDT
Description of problem: While logging out in JSON from camel app via Log4j2 JSONLayout [1] but when looking in Kibana, the "message" field is empty but everything else is imported and works fine. {"timeMillis":1459853347608,"thread":"main","level":"INFO","loggerName":"org.apache.camel.spring.SpringCamelContext","message":"Total 1 routes, of which 1 is started.","endOfBatch":false,"loggerFqcn":"org.apache.logging.slf4j.Log4jLogger"} [1]https://logging.apache.org/log4j/2.x/manual/layouts.html#JSONLayout Culprit: https://github.com/openshift/origin-aggregated-logging/blob/master/fluentd/configs.d/filter/k8s_record_transform.conf#L6 Overwrites the message field, regardless if it's set or not. Version-Release number of selected component (if applicable): 3.1.1.6 Addition Info: http://post-office.corp.redhat.com/archives/openshift-sme/2016-April/msg00236.html
"log" is elsewhere set based on several other potential fields, but not "message" specifically. It should be a simple patch to make it based on "message" as well if that's present. In general, we should probably make an effort to normalize any meaningful fields before removing them.
Hi team, is there any news on this bugzilla please? Regards, Julia Ievstignieieva Operations Support Team lead GSS EMEA
Should be in image openshift3/logging-fluentd:3.2.0-8
It's fixed, tested with openshift3/logging-fluentd:3.2.0-8(ImageId: e1a07eb99c), please refer to the test result in attachment named "message field shown in kibana".
Created attachment 1157786 [details] message field shown in kibana
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/RHSA-2016:1094