Hi,
On Thu, 5 Dec 2013 11:19:49 -0800 (PST)
M Mir wrote:
> Will this work?
I see no problems with the config. Go and try it, the success depends on
your environment also, there are other places where things may not work
as expected (receiver syslog server, application generating the CSV).
> A
OK my bad I removed syslog extension... I added it
## This is a sample configuration file. See the nxlog reference manual about the
## configuration options. It should be installed locally and is also available
## online at http://nxlog.org/nxlog-docs/en/nxlog-reference-manual.html
## Please set
Thank you for the quick reply ! Sorry for my ignorance this is my very first
time using NXlog, AWESOME product from what I can see so far (I really am
trying , RTFM, google, etc. :-) ) : so given the information I gave earlier and
the information you gave, thank you again I have chagned my conf
Hi,
Syslog is not structured , so I don't see the point in parsing the CSV
before forwarding it. It needs to be parsed on the receiver side.
Just add "Exec to_syslog_bsd();" to your output module and remove the csv
instance.
Regards,
Botond
On Thu, 5 Dec 2013 10:36:18 -0800 (PST)
M Mir wrote:
I have a pretty easy question (i'm brand new and just finished really that
manual), I am running nxlog on a Windows Server. We have a process that runs
daily at 5am and usually finishes by 6am, it produces a CSV (Saved in
D:\Program Files (x86)\FileSeek\filename.csv) in this format:
"File","
