Why Filebeat returns Unicode character code instead of XML tag symbol under message, it is showing like \u003c and \u003e

[elastikip]

what version of beats are you using? I found this thread that talks about filebeat behavior in possibly older versions...

Beats encodes angle brackets ("<" and ">") as \u003c and \u003e in JSON output

I'm in the process of setting up filebeat to ship out logs on some of my servers. One of my logs has angle brackets in it ("<" and ">"). Once filebeat processes it and outputs its JSON representation, those angle brackets have been replaced with \u003c and \u003e, respectively. Sample log: Sep 15 17:49:02 [26263] <warning> [rest of log omitted] JSON output: { "@timestamp":"2016-09-16T01:06:24.394Z", "beat":{ "hostname":"[redacted]", "name":"[redacted]" }, "input_type…