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 to this:
############################################################
## 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 the ROOT to the folder your nxlog was installed into,
## otherwise it will not start.
#define ROOT C:\Program Files\nxlog
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
#<Input in>
# Module im_msvistalog
# For windows 2003 and earlier use the following:
# Module im_mseventlog
#</Input>
<Input in>
Module im_file
File "D:\\Program Files (x86)\\FileSeek\\T_Drive_Scan_csv_output.csv"
</Input>
<Output out>
Module om_udp
Host 172.30.140.100
Port 514
Exec to_syslog_bsd();
</Output>
<Route 1>
Path in => out
</Route>
##############################################################
Will this work? Also since this file is generated and replaced every morning
at 5am how/when nxlog know to send this?
Thank you again!
On Thursday, December 5, 2013 1:48 PM, Botond Botyanszki <b...@nxlog.org> wrote:
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 <mmu...@yahoo.com> 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","Path","Line #","File Size","Date Created","Date Accessed","Date
>> Modified","Line"
>> "amazonwebservices.com.website","\\xxxxxxx.intra.xxxxxxxxx.com\Temp\Bill\AWS","7","460","Dec
>> 04, 2013 10:10","Dec 04, 2013 10:10","Dec 04, 2013
>> 10:10","Prop2=65,2C0000000000000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF6E0000005C000000C30500007403000026"
>> "DATA_MGMT.XML","\\xxxxxxx.intra.xxxxxxx.com\Temp\cmahany","1","1,629,877","Dec
>> 03, 2013 09:38","Dec 03, 2013 09:38","Dec 03, 2013 09:38","(more)
>> ACCOUNTMANAGERID NULL 0 105 50 1153 50 0 varchar2 25 0 ELEMITEM NO NOT A KEY
>> 0 0 INTERNALSERVICEREP(more)"
>> "DWR.XML","\\xxxxxx.intra.xxxxxxxx.com\Temp\cmahany","1","2,109,524","Dec
>> 03, 2013 09:35","Dec 03, 2013 09:35","Dec 03, 2013 09:36","(more) 0 0
>> ALTERNATE_ID NULL 0 129 20 1929 20 0 number 26 0 ELEMITEM NO NOT A KEY 24 0
>> PERSON_SK NULL 0 12(more)"
>>
>> Ultimately I want to forward this to a syslog server at 172.30.140.100, also
>> I would like to add the word "Scanner", to EACH line. Also I if you notice
>> is delimited by a "," and by "s to avoid confusion with dates (which also
>> has a comma) what kind of configuration file do I need? this is what I have
>> so far:
>>
>>
>> ###############################################################
>> ## 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 the ROOT to the folder your nxlog was installed into,
>> ## otherwise it will not start.
>>
>> #define ROOT C:\Program Files\nxlog
>> 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
>>
>> #<Input in>
>> # Module im_msvistalog
>> # For windows 2003 and earlier use the following:
>> # Module im_mseventlog
>> #</Input>
>>
>> <Extension syslog>
>> Module xm_syslog
>> </Extension>
>>
>> <Extension csv>
>> Module xm_csv
>> Delimiter ,
>> </Extension>
>>
>> <Input file_watch>
>> Module im_file
>> File "D:\\Program Files (x86)\\FileSeek\\T_Drive_Scan_csv_output.csv"
>> </Input>
>>
>>
>> <Output out>
>> Module om_tcp
>> Host 172.30.140.100
>> Port 514
>> </Output>
>>
>> <Route 1>
>> Path in => out
>> </Route>
>>
>> ###############################################################
>> Do will this work? what format will it send this to the syslog server? do I
>> nee to choice "outputtype"? What does that give?
>
>------------------------------------------------------------------------------
>Sponsored by Intel(R) XDK
>Develop, test and display web and hybrid apps with a single code base.
>Download it for free now!
>http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
>_______________________________________________
>nxlog-ce-users mailing list
>nxlog-ce-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
>
>
>
>
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
