<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: delimited by comma but not .csv file in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299339#M96058</link>
    <description>&lt;P&gt;For this source, set up your props.conf with these and it should extract correctly.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;FIELD_DELIMITER = ,
FIELD_QUOTE = "
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 16 Feb 2017 19:24:06 GMT</pubDate>
    <dc:creator>DalJeanis</dc:creator>
    <dc:date>2017-02-16T19:24:06Z</dc:date>
    <item>
      <title>delimited by comma but not .csv file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299337#M96056</link>
      <description>&lt;P&gt;I have a jobinfo.log file in my server, it was delimited by comma but not [xxxx.csv] file.&lt;BR /&gt;
So it can not be added into index just like [.csv].&lt;/P&gt;

&lt;P&gt;I don't want to change the extension from [.log] to [.csv],but the extension has to be changed ?&lt;/P&gt;

&lt;P&gt;Below is the jobinfo.log file &lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;80925610,00004105,00000000,10660,"20170213140245","20170213140245",1,0,0,"ro,o,t","root"&lt;BR /&gt;
80925612,00004106,00000000,10660,"20170213140250","20170213140250",1,0,0,"ro,o,t","root"&lt;BR /&gt;
80925626,00004125,00000000,10660,"20170213140411","20170213140411",1,0,0,"ro,o,t","root"&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;You can see that the comma also in double quotation, so if the extension is not [.csv] then the result will be below&lt;/P&gt;

&lt;P&gt;1,0,0,"ro,o,t","root" -&amp;gt; 1,0,0,ro,o,t,root         #the string "ro,o,t" also be delimited by comma&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 02:26:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299337#M96056</guid>
      <dc:creator>kavana</dc:creator>
      <dc:date>2017-02-15T02:26:11Z</dc:date>
    </item>
    <item>
      <title>Re: delimited by comma but not .csv file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299338#M96057</link>
      <description>&lt;P&gt;So are you just trying to bring this data in so that it will be separated into fields like a csv would be?&lt;/P&gt;

&lt;P&gt;In that case bring the data in as a sourcetype (preferably unique sourcetype name), open it in search, expand one line, click "Event Actions" and use the field extractor. Choose "delimiters" , choose comma, and name the fields. This will create a transforms and props.conf for this sourcetype. &lt;/P&gt;

&lt;P&gt;Or edit the transforms &amp;amp; props.conf files &lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/170251/how-to-extract-two-fields-separated-by-delimiter-c.html"&gt;https://answers.splunk.com/answers/170251/how-to-extract-two-fields-separated-by-delimiter-c.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 18:07:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299338#M96057</guid>
      <dc:creator>JDukeSplunk</dc:creator>
      <dc:date>2017-02-16T18:07:53Z</dc:date>
    </item>
    <item>
      <title>Re: delimited by comma but not .csv file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299339#M96058</link>
      <description>&lt;P&gt;For this source, set up your props.conf with these and it should extract correctly.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;FIELD_DELIMITER = ,
FIELD_QUOTE = "
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 16 Feb 2017 19:24:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299339#M96058</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-02-16T19:24:06Z</dc:date>
    </item>
    <item>
      <title>Re: delimited by comma but not .csv file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299340#M96059</link>
      <description>&lt;P&gt;It doesn't have to be a &lt;CODE&gt;*.csv&lt;/CODE&gt; file to be able to use the sourcetype definition (event breaking, timestamp recognition etc) of built-in sourcetype &lt;CODE&gt;csv&lt;/CODE&gt;. When you setup the data monitoring (input.conf), just explicitly assign the sourcetype as "csv".&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 20:07:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299340#M96059</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-02-16T20:07:50Z</dc:date>
    </item>
    <item>
      <title>Re: delimited by comma but not .csv file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299341#M96060</link>
      <description>&lt;P&gt;thank you so much!&lt;/P&gt;

&lt;P&gt;it's worked !&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2017 00:16:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/delimited-by-comma-but-not-csv-file/m-p/299341#M96060</guid>
      <dc:creator>kavana</dc:creator>
      <dc:date>2017-02-17T00:16:21Z</dc:date>
    </item>
  </channel>
</rss>

