Hi Botond,
Thanks for a great product.
A few years [1] ago you explained that messages like these:
2015-07-09 15:32:24 ERROR binary logdata (66939 bytes) does not fit in
output buffer (size: 65000 bytes), dropping
2015-07-09 15:32:41 ERROR binary logdata (106865 bytes) does not fit in
output buffer (size: 65000 bytes), dropping
2015-07-09 15:32:42 ERROR binary logdata (103947 bytes) does not fit in
output buffer (size: 65000 bytes), dropping
are due to the size of NX_OUTPUT_BUFSIZE being fixed at 65000. You also
indicated it was difficult to do a custom Windows build.
I have bumped into this issue again as per the above and am trying to find
out what the best way is to get a Windows MSI that can handle larger lines
because I have a lot of them and I would love to feed them to NXLOG.
Perhaps I should switch to using plain TCP? But then I would have to format
the raw message as JSON and parse it back into fields on the receiving end?
This seems like it could work but not very efficient.
What do you recommend?
Thanks.
-Slim
[1]
http://nxlog-ce-users.narkive.com/Cj8NcZEh/binary-logdata-does-not-fit-in-output-buffer
--
Jeroen "Slim" van Gelderen
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
