Can't solve this problem of: oversized string, limit is 1048576 bytes

This is a lengthy description but pelase bear with me, I'm really starting to loose hope here...

So I have tried to catch this "oversized string" and avoid it braking my logging but am not able to, even writing debug log failed.

Here is the nxlog.log where you can see that it broke at 5:30, then source log changed and then it broke again and after that it wrote no more to debug nor to syslog anything:

AskedApril 17, 2015 - 10:10am

Appending GUID to logs

I am trying to append a pre-defined GUID to some application log files. The log files are written in JSON and I would like to append these logs with a GUID. 

I have defined the GUID in my config file with the variable CUSTOMER_TOKEN.

AskedApril 17, 2015 - 8:44am

using xm_multiline


I'm looking to use the xm_multiline extension to try to concatinate log messages that all fall under the same headerline, but to this point have had little luck.  All messages begin with either -E, -A, -W, -I, and all proceeding lines with "at" are part of the same message.

Any assistance would be appreciated.

Using nxlog.conf:

AskedApril 15, 2015 - 9:31pm

Nxlog-ce memory leak?


Has anyone observed any memory leaks with the community edition of nxlog v2.1.2148 on Windows (2008R2, 2012, and 2012R2)?

AskedApril 15, 2015 - 3:07pm