Hi,
Yes, another option is to remove the offending byte:
Exec $raw_event = replace($raw_event, "\x61", "");
Regards,
Botond
On Fri, 27 Jan 2017 11:23:45 +0100
Ruth Garzón wrote:
> hi!
>
> thanks. I created a dump but I was not able to find there the same log that
> is causing me issues.
> I
hi!
thanks. I created a dump but I was not able to find there the same log that
is causing me issues.
I think at this moment the error comes because it is trying to reload an
old file which contains that character.
The encoding in IIS for the Logging is UTF-8 and in the IISLogs the
character is wr
Hi,
You could dump the json into a file and check if the encoding is wrong
and to help figure out how to convert it correctly:
Exec file_write("tmp/output.log",to_json() + "\n");
BTW, there is an enhancement for xm_json to ensure that the generated
JSON is valid UTF-8. This is currently in the
Hi,
some weeks ago we suddenly had some parsing issues with nxlog that we never
had before. Nxlog is constantly logging this error:
*ERROR HTTP response status is not OK: 400 Bad Request* (which refers that
the json we try to send to Elasticsearch is not well formed)
In Elasticsearch we found th
