<?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: Second index with fewer fields in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Second-index-with-fewer-fields/m-p/47677#M96732</link>
    <description>&lt;P&gt;Can you give me quick example of what my conf files would look like?&lt;/P&gt;</description>
    <pubDate>Thu, 28 Feb 2013 22:52:36 GMT</pubDate>
    <dc:creator>tnkoehn</dc:creator>
    <dc:date>2013-02-28T22:52:36Z</dc:date>
    <item>
      <title>Second index with fewer fields</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Second-index-with-fewer-fields/m-p/47675#M96730</link>
      <description>&lt;P&gt;I have large CDR records that are going to one index (let's call it index1). I need a second index (let's call it index2) that only uses a subset of the fields in the CDR records without messing up index1. For example, a CDR record looks like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;field1|field2|field3|...............|field200
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I want index2 to only have these fields:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;field20,field30,field33,field101,field150,field172
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I know I can get these fields using regex in transforms.conf but just need to know (if possible) what to do in props and transforms to get these fields in index2.&lt;/P&gt;

&lt;P&gt;The current props.conf looks like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[index1]
REPORT-parsefields = index1_parse
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The current transforms.conf looks like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[index1_parse]
DELIMS = "|"
FIELDS = "field1", "field2", "field3",......."field200"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 28 Feb 2013 22:04:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Second-index-with-fewer-fields/m-p/47675#M96730</guid>
      <dc:creator>tnkoehn</dc:creator>
      <dc:date>2013-02-28T22:04:27Z</dc:date>
    </item>
    <item>
      <title>Re: Second index with fewer fields</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Second-index-with-fewer-fields/m-p/47676#M96731</link>
      <description>&lt;P&gt;You could set up indexer1 to forward this data to indexer2 on top of indexing it itself. Then tell indexer2 to apply a huge SEDCMD to the data that strips out the first nineteen fields, keeps the 20th, strips out nine, keeps the 30th, and so on.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 22:31:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Second-index-with-fewer-fields/m-p/47676#M96731</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2013-02-28T22:31:42Z</dc:date>
    </item>
    <item>
      <title>Re: Second index with fewer fields</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Second-index-with-fewer-fields/m-p/47677#M96732</link>
      <description>&lt;P&gt;Can you give me quick example of what my conf files would look like?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 22:52:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Second-index-with-fewer-fields/m-p/47677#M96732</guid>
      <dc:creator>tnkoehn</dc:creator>
      <dc:date>2013-02-28T22:52:36Z</dc:date>
    </item>
  </channel>
</rss>

