Description of problem: Fluentd now adds the complete record to ES, adding uneeded noise and space usage to the ES cluster. Version-Release number of selected component (if applicable): logging-fluentd v3.5.5.31.66-54
What is the severity of this problem? Is it worth fixing in 3.5, if the problem has been fixed in 3.6 and later and can be resolved by upgrading?
I don't think a fix for 3.5 is warranted at this point.
Closing based on #c5 an fixed in 3.6 and later
(In reply to François Cami from comment #5) > I don't think a fix for 3.5 is warranted at this point. Just to confirm: the record should look like https://bugzilla.redhat.com/show_bug.cgi?id=1567991#c1 _except_ that the "message" field should look like this: "message":"10.129.0.1 [13/Apr/2018:16:00:36 +0200] GET /CCC/ HTTP/1.1 200 320 0" instead of containing the embedded JSON document I don't suppose you could test this on OCP 3.6 or later, to see if it is fixed there? The code is quite different in 3.6 and later.
Rich, it will be tested in the following weeks, on 3.6+.
Tested and fixed in 3.9.