2
responses

Hello,
I have two questions.

First, a latest nxlog-ce formally supports Windows Server 2016 ?
I saw the following url, and now it seems to support the Windows Server 2016.

https://nxlog.co/documentation/nxlog-user-guide/platforms.html

Second, the eventlog source limitation on Windows Server 2016 (the OS have over 256 sources, but the nxlog could treat up to 256 sources) is solved ?
I saw the following forum questions.

https://nxlog.co/question/2594/256-sources-limit
https://nxlog.co/question/3200/eventlog-source-limitation-server-2016

AskedDecember 10, 2018 - 3:31am

Answers (2)

Hello,

Yes, Windows 2016 is supported.

The 256 limitation is still on the roadmap to be fixed in the CE version. The CE version is a volunteer effort, as such there is no ETA.
This limitation was fixed in the EE version. Depending on how important this is to your organization , you could split the source channels like suggested in the links.
NXLog EE is also available as a trial, if you would like to see if EE will work for you.

Thank you,
Jesse

Hi
I faced this issue as well today and solved this way, hope this helps others

Cheers Chris

#------------------------------------------------ nxlog.conf -----------------------------------------
define ROOT C:\Program Files (x86)\nxlog

Moduledir %ROOT%\modules
CacheDir %ROOT%\data
Pidfile %ROOT%\data\nxlog.pid
SpoolDir %ROOT%\data
LogFile %ROOT%\data\nxlog.log

<Extension gelf>
Module xm_gelf
</Extension>

<Input in_app>
Module im_msvistalog
Query <QueryList><Query Id="0"><Select Path="Application">*</Select></Query></QueryList>
Exec $Hostname = hostname();
</Input>
<Input in_sys>
Module im_msvistalog
Query <QueryList><Query Id="0"><Select Path="System">*</Select></Query></QueryList>
Exec $Hostname = hostname();
</Input>
<Input in_sec>
Module im_msvistalog
Query <QueryList><Query Id="0"><Select Path="Security">*</Select></Query></QueryList>
Exec $Hostname = hostname();
</Input>

<Output out>
Module om_udp
Host syslog.domain.local
Port 2016
OutputType GELF
</Output>

<Route oute_app>
Path in_app => out
</Route>
<Route oute_sys>
Path in_sys => out
</Route>
<Route oute_sec>
Path in_sec => out
</Route>
# ------------------------------------------------------------------------------------------------------