Dear Members of Nxlog Sourceforge Mailing List,
As of 1 April, NXLog is going to terminate its current mailing list on
Sourceforge. If you would like to stay in touch with the community, please
provide your details here<https://nxlog.co/user/register> to register.
Hope to see yo
Good day,
Attached is my current working nxlog.conf file.
I am enabling reporting on successful login events (eventID 4624) and need to
push that to NXLog.
Including this eventID is not a problem.
What IS a problem is the filtering of the events that is sent to our Graylog.
This is an Exchange
m mytable
>
>
> $SyslogFacility = 'local5';
> $SourceName = $APP_NAME;
> $Hostname = "myhostname";
> $Message = $MESSAGE";
>
>
>
>
> Has anyone worked with the im_dbi (or om_dbi) to an
Thanks Botond,
The NSSM would generate Ctrl-C input on the console. Would this do?
Alternatively, it notifies the threads of the application with /WM_QUIT/
message. Would that be handled in NXLog?
ref http://nssm.cc/usage#shutdown
Kind regards, Rob
On 07/18/14 21:32, nxlog-ce-users-requ
ne in c#. Would there be much
> concern in nxlog.exe regarding service signals and how about shutting
> down gracefully if I wrap the process say with srvany and cmd script or
> with custom c# service?
>
> Thanks and regards, Rob
>
>
> On 07/17/14 13:09, nxlog-ce-users-requ.
write one in c#. Would there be much
concern in nxlog.exe regarding service signals and how about shutting
down gracefully if I wrap the process say with srvany and cmd script or
with custom c# service?
Thanks and regards, Rob
On 07/17/14 13:09, nxlog-ce-users-requ...@lists.sourceforge.net
cal UDP sink is part of my design and hence I'm wondering if there's
some simple way to prop the process priority of nxlog on windows
(windows 2008 server actually). I wouldn't fancy some brutal external
scripts but well if it hs to be... Wish it was linux easy.
I have a mix of Network Devices, Firewalls, Medical Devices, and Windows
machines I want to gather logs from.
I DO NOT want to put another agent on all my Windows machines, or on other
devices around the network.
Is NXLOG suitable for this scenario? Or does it still need an agent on
Windows
