<?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: Field extraction and conditional splitting into different indexes on a heavy forwarder in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-and-conditional-splitting-into-different/m-p/240582#M71512</link>
    <description>&lt;P&gt;Sorry, won't work &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Lookups and field extractions using &lt;CODE&gt;EXTRACT&lt;/CODE&gt; are a search time function, and cannot be made to "fire" during index time pipeline processing.  You'll need to come up with another way of accomplishing index-time routing - probably based on regex alone.&lt;/P&gt;</description>
    <pubDate>Wed, 29 Jun 2016 17:10:14 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2016-06-29T17:10:14Z</dc:date>
    <item>
      <title>Field extraction and conditional splitting into different indexes on a heavy forwarder</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-and-conditional-splitting-into-different/m-p/240581#M71511</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;In my environment I have a setup of two heavy forwarders forwarding to a set of clustered indexers.&lt;BR /&gt;
I want those forwarders to receive syslog, and depending on the facility/severity the incoming data should be forwarded to different indexes.&lt;/P&gt;

&lt;P&gt;To get the syslog facility/severity, I want to do a lookup for the priority I receive in the event. To do that lookup, I figured I need a named field for the priority.&lt;BR /&gt;
So I created an app for those forwarders with the following:&lt;/P&gt;

&lt;P&gt;props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[generic_syslog]
EXTRACT-extract_syslog_priority = ^&amp;lt;(?&amp;lt;syslog_priority&amp;gt;\d+)&amp;gt; 
LOOKUP-lookup_syslog_priority = syslog_priority_lookup syslog_priority OUTPUTNEW syslog_facility, syslog_severity
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;transforms.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[syslog_priority_lookup]
filename = syslog_priorities.csv
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, above config does not seem to work. The indexed events have no fields as "syslog_priority", nor "syslog_facility" or the severity.&lt;/P&gt;

&lt;P&gt;What am I getting wrong here?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:07:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-and-conditional-splitting-into-different/m-p/240581#M71511</guid>
      <dc:creator>wirelessy</dc:creator>
      <dc:date>2020-09-29T10:07:15Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction and conditional splitting into different indexes on a heavy forwarder</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-and-conditional-splitting-into-different/m-p/240582#M71512</link>
      <description>&lt;P&gt;Sorry, won't work &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Lookups and field extractions using &lt;CODE&gt;EXTRACT&lt;/CODE&gt; are a search time function, and cannot be made to "fire" during index time pipeline processing.  You'll need to come up with another way of accomplishing index-time routing - probably based on regex alone.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jun 2016 17:10:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-and-conditional-splitting-into-different/m-p/240582#M71512</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2016-06-29T17:10:14Z</dc:date>
    </item>
    <item>
      <title>Re: Field extraction and conditional splitting into different indexes on a heavy forwarder</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-and-conditional-splitting-into-different/m-p/240583#M71513</link>
      <description>&lt;P&gt;Well, that does indeed explain what I am getting wrong :). Thank you!&lt;BR /&gt;
I took that idea off of this app: &lt;A href="https://splunkbase.splunk.com/app/736/"&gt;https://splunkbase.splunk.com/app/736/&lt;/A&gt;&lt;BR /&gt;
Am I correct on the assumption this would work again, if it wasn't for my 6.4.1 heavy forwarder, but 6.3 or older?&lt;/P&gt;

&lt;P&gt;Sadly, I am left alone in the field with (so far) zero experience in configuring Splunk.&lt;BR /&gt;
I don't think I fully understand what possibilities I have to achieve that, and where/how to configure those. Could you provide me with a possible way, or just a keyword that I can go dig into?&lt;/P&gt;

&lt;P&gt;Maybe a similar example, on which I can go full copycat again?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2016 13:53:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-and-conditional-splitting-into-different/m-p/240583#M71513</guid>
      <dc:creator>wirelessy</dc:creator>
      <dc:date>2016-06-30T13:53:09Z</dc:date>
    </item>
  </channel>
</rss>

