<?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: How to route data from forwarders to separate indexes based on the source field when data is coming from single TCP port? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-route-data-from-forwarders-to-separate-indexes-based-on/m-p/212674#M41817</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Short answer&lt;/STRONG&gt;&lt;BR /&gt;
Universal Forwards can't inspect data. Heavy Forwarders (and Indexers) can.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Long answer&lt;/STRONG&gt;&lt;BR /&gt;
Use regex to parse the values of your JSON events and then redirect (override) accordingly to the right index.&lt;BR /&gt;
See this:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/6623/conditional-index-and-sourcetype-name-inputs-conf-by-file-naming-convention.html"&gt;https://answers.splunk.com/answers/6623/conditional-index-and-sourcetype-name-inputs-conf-by-file-naming-convention.html&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/246672/how-can-i-override-an-index-name-based-on-sourcety.html"&gt;https://answers.splunk.com/answers/246672/how-can-i-override-an-index-name-based-on-sourcety.html&lt;/A&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Advancedsourcetypeoverrides"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Advancedsourcetypeoverrides&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 19 Feb 2016 14:03:41 GMT</pubDate>
    <dc:creator>javiergn</dc:creator>
    <dc:date>2016-02-19T14:03:41Z</dc:date>
    <item>
      <title>How to route data from forwarders to separate indexes based on the source field when data is coming from single TCP port?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-route-data-from-forwarders-to-separate-indexes-based-on/m-p/212673#M41816</link>
      <description>&lt;P&gt;I have log data from multiple sources coming into a single TCP port in JSON format as below:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;01&amp;gt;- hostname {"name":"DefaultProfile","version":"1.0","isonjkpFormat":"yyyy-MM-dd'T'HH:mm:ss.SSSZ","type":"Event","category":"RT_FLOW_SESSION_CREATE_LS" [helps@2222.2.2.2.2.22 localis-compute-zxcv=\"ABC1\" application=\"UNKNOWN\" MKUNJI-application=\"UNKNOWN\" mnbhyujgt=\"UNKNOWN\"]","bgasbnJuh":"1","mnbIPOUN":"other","absIPPOL":"other","qweTgvfrt":"minj-bag6-7856ab-Hnqasui","abcPecpokk":"och-00-145-987.Net_11_4_5_6","mnbJhbpoiu":"other","source":"My application1","nhjRkyhcfBhytf":"MKI-PLO-ASW","thuHyrtfcQhbnjuytfv":"192.168.1.11"}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;From this input, I want to forward the data to separate indexes based on the values for the source field.&lt;/P&gt;

&lt;P&gt;Example: if source: application1, then send to index1, and so on.&lt;BR /&gt;
Does the Splunk forwarder have this capability to extract a field and segregate the events to separate indexes on the indexer?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2016 10:00:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-route-data-from-forwarders-to-separate-indexes-based-on/m-p/212673#M41816</guid>
      <dc:creator>bkumarm</dc:creator>
      <dc:date>2016-02-19T10:00:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to route data from forwarders to separate indexes based on the source field when data is coming from single TCP port?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-route-data-from-forwarders-to-separate-indexes-based-on/m-p/212674#M41817</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Short answer&lt;/STRONG&gt;&lt;BR /&gt;
Universal Forwards can't inspect data. Heavy Forwarders (and Indexers) can.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Long answer&lt;/STRONG&gt;&lt;BR /&gt;
Use regex to parse the values of your JSON events and then redirect (override) accordingly to the right index.&lt;BR /&gt;
See this:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/6623/conditional-index-and-sourcetype-name-inputs-conf-by-file-naming-convention.html"&gt;https://answers.splunk.com/answers/6623/conditional-index-and-sourcetype-name-inputs-conf-by-file-naming-convention.html&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/246672/how-can-i-override-an-index-name-based-on-sourcety.html"&gt;https://answers.splunk.com/answers/246672/how-can-i-override-an-index-name-based-on-sourcety.html&lt;/A&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Advancedsourcetypeoverrides"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Advancedsourcetypeoverrides&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2016 14:03:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-route-data-from-forwarders-to-separate-indexes-based-on/m-p/212674#M41817</guid>
      <dc:creator>javiergn</dc:creator>
      <dc:date>2016-02-19T14:03:41Z</dc:date>
    </item>
  </channel>
</rss>

