There is definitely nested json, but this is being handled fine on other
hosts running the same version of nxlog. here is a sample of the json:
{"timestamp":"2016-06-27T19:35:52.140960+0100","level":"info","message":"publishing
check result","payload":{"client":"test-host.domain.com
","check":{"n
Hi,
This is most likely caused by some nested JSON in the input.
Do you have a sample for that?
Regards,
Botond
On Thu, 23 Jun 2016 11:14:44 -0700
tombin wrote:
> I have several instances in aws running nxlog without any issue. I have 1
> box that acts funny and does not parse the json log (t
