Debug that writes out only the lines that have problems

I have looked at debugging options but they all seem to write out any message that arrives but is there an option to write the raw message to debug log only if there is a problem with parsing of this message?

AskedApril 15, 2015 - 2:33pm

Common format for Windows, internal logs and my app logs

TL;DR: what's the recommended way of converting logs to a common (e.g. GELF) format?

I'm using NXLog together with Logstash and EalsticSearch. I'm collecting logs from Windows, NXLogs (internal) and my app logs using line based JSON.

AskedApril 12, 2015 - 3:16pm

64-bit Windows Event Log support - Community vs. Enterprise

Dear NxLog Community,

I've heard some debate lately as to the question of 64-bit Windows support with NxLog.  One camp claims that the NxLog "Community Edition" cannot export Event Logs from 64-bit Windows systems, a.k.a Server 2008 R2 and Server 12.  These folks argue that to get 64-bit Windows support the NxLog Enterprise Edition is required.

AskedApril 10, 2015 - 4:07pm

NXLog and Windows WUS - can not work together


I had install NXLog agent on domain controllers with WUS.


Installation ik, doomain is ok.

But I see in NXlog.log this:


INFO reconnecting in 1 seconds
ERROR om_tcp send failed; An established connection was aborted by the software in your host machine.


AskedApril 6, 2015 - 9:20am

Custom tags

Can I insert a custom tag (right now it is not present "-" ) somehow like this maybe:
<Input hl7out>
Module         im_file
File         'C:\Connectivity\mcf\log\hl7out.log'
Exec        $tag = hl7out

AskedApril 2, 2015 - 3:05pm