<?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: TCP:514 Input -&amp;gt; Multiple Indexex and Source Type in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243324#M47154</link>
    <description>&lt;P&gt;Thank you. It worked.&lt;BR /&gt;
In case I would like to classify each index with a different sourcetype. How can I do that?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Lp&lt;/P&gt;</description>
    <pubDate>Wed, 24 Aug 2016 12:18:58 GMT</pubDate>
    <dc:creator>lpolo</dc:creator>
    <dc:date>2016-08-24T12:18:58Z</dc:date>
    <item>
      <title>TCP:514 Input -&gt; Multiple Indexex and Source Type</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243322#M47152</link>
      <description>&lt;P&gt;I have a TCP:514 input working without any problem but indexing in a single index. &lt;BR /&gt;
 I have not found a way to index events  as follow:&lt;/P&gt;

&lt;P&gt;Event A should be indexed in index=A&lt;BR /&gt;
_time host="a.com" Type="A" ....... Any Key Value Pair&lt;/P&gt;

&lt;P&gt;Event B should be indexed in index=B&lt;BR /&gt;
_time host="a.com" Type="B" ....... Any Key Value Pair&lt;/P&gt;

&lt;P&gt;How can I do that?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Lp&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2016 18:14:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243322#M47152</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2016-08-23T18:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: TCP:514 Input -&gt; Multiple Indexex and Source Type</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243323#M47153</link>
      <description>&lt;P&gt;The Splunk Add-on for Cisco ASA (&lt;A href="https://splunkbase.splunk.com/app/1620/"&gt;https://splunkbase.splunk.com/app/1620/&lt;/A&gt;) does something similar with sourcetypes.  Using that add-on as an example, your props.conf should look something like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::tcp:514]
TRANSFORMS-force_indexes = force_index_A,force_index_B
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Your transforms.conf should look something like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[force_index_A]
DEST_KEY = _MetaData:Index
REGEX = Type="A"
FORMAT = A

[force_index_B]
DEST_KEY = _MetaData:Index
REGEX = Type="B"
FORMAT = B
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 23 Aug 2016 20:15:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243323#M47153</guid>
      <dc:creator>jconger</dc:creator>
      <dc:date>2016-08-23T20:15:54Z</dc:date>
    </item>
    <item>
      <title>Re: TCP:514 Input -&gt; Multiple Indexex and Source Type</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243324#M47154</link>
      <description>&lt;P&gt;Thank you. It worked.&lt;BR /&gt;
In case I would like to classify each index with a different sourcetype. How can I do that?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Lp&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2016 12:18:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243324#M47154</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2016-08-24T12:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: TCP:514 Input -&gt; Multiple Indexex and Source Type</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243325#M47155</link>
      <description>&lt;P&gt;If you want to do index and sourcetype, your props.conf should look like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::tcp:514]
TRANSFORMS-force_indexes = force_index_A,force_index_B,force_sourcetype_A,force_sourcetype_B
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And your transforms.conf file should look like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[force_index_A]
DEST_KEY = _MetaData:Index
REGEX = Type="A"
FORMAT = A

[force_index_B]
DEST_KEY = _MetaData:Index
REGEX = Type="B"
FORMAT = B

[force_sourcetype_A]
DEST_KEY = MetaData:Sourcetype
REGEX = Type="A"
FORMAT = sourcetype::sourcetype_A

[force_sourcetype_B]
DEST_KEY = MetaData:Sourcetype
REGEX = Type="B"
FORMAT = sourcetype::sourcetype_B
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 24 Aug 2016 15:42:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243325#M47155</guid>
      <dc:creator>jconger</dc:creator>
      <dc:date>2016-08-24T15:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: TCP:514 Input -&gt; Multiple Indexex and Source Type</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243326#M47156</link>
      <description>&lt;P&gt;Thanks for the example. &lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2016 16:55:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-514-Input-gt-Multiple-Indexex-and-Source-Type/m-p/243326#M47156</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2016-08-24T16:55:19Z</dc:date>
    </item>
  </channel>
</rss>

