Dear Nxlog community, Hi. Special thanks to the development team that
brought us this exceptional piece of software.
I have the following use-case: It might happen that application logging is
miss-implemented and can produce a large output in one single line. For
everything, one liner, greater than 1 mega byte, Nxlog will trigger the
following error message: "ERROR string limit (1048576 bytes) reached". The
problem is that all the files monitored under that input type, "nxlog.conf"
wise, will be drop from the processing queue. That happens silently.
My question is whether this is known or not and is that a feature or a bug?
Regards, Andrei
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
