Routing messages based on type and source in a client server configuration

Currently process and transform the windows event/iis logs on the client, however as I have more servers I am wondering about routing everything to a central point using the binary format and then processing them into the relevant tables in to a mysql db. I am struggling with at which stage this filtering and tansforming is done and what the route should look like. Do I use the patern filter in a process stage and then use and if statement in the route based on the patern id?

AskedOctober 21, 2014 - 11:41am

xm_perl.dll is not present in extension directory

I am trying to use the perl extension in Windows, but nxlog complains that it cannot find the xm_perl.dll. The complaint is correct, the file is not there. My question is why? Does the windows version not support using perl?

AskedOctober 8, 2014 - 1:59pm

Windows Nxlog creating multiple dyn$ folders


I really would like some assistance in the forum - 

Here is the scenario:

Installed nxlog.c.e in Windows 2008 R2

Used the query list -to get security logs

Added that in the module - started the server - everything is fine.

I tested this in my Windows mahcine - to my Redhat server.


The issue happens when the Windows machine is registered to the domain.

AskedOctober 7, 2014 - 9:41am

Upgrade to 2.8 on Debian Wheezy

I am unable to find the dependencies for wheezy. apt-get -f install simply removes nxlog. My version of debian is : Linux chis-logcollector 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux Install pkg: nxlog-ce_2.8.1248_amd64.debian-wheezy.deb Is there a plan to include dependencies as this is a rather flaky way of installation? Thanks Ash Kumar
AskedSeptember 19, 2014 - 3:18pm