<?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: Syslog UDP data filtering to index in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-UDP-data-filtering-to-index/m-p/46382#M8729</link>
    <description>&lt;P&gt;filter on the heavy forwarder if you have any, otherwise on the indexer  (the instance that will be Parsing the events first)&lt;BR /&gt;
you can see this page for nullQueue examples :&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.4/Deploy/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.4/Deploy/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 27 Aug 2013 15:11:03 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2013-08-27T15:11:03Z</dc:date>
    <item>
      <title>Syslog UDP data filtering to index</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-UDP-data-filtering-to-index/m-p/46381#M8728</link>
      <description>&lt;P&gt;We have data that comes into UDP port 514 on a heavy forwarder that we than send to our indexers.  The data looks like the below:&lt;/P&gt;

&lt;P&gt;Aug 26 12:23:19 10.142.102.50 Aug 26 12:23:18 pl-wlmuatdp4 [&lt;STRONG&gt;in01_sr&lt;/STRONG&gt;][latency][info] wsgw(AutoPolicyManager): trans(76922997)[10.142.99.6]: Latency:   0  47   0  15  47  10   0 194 241 195 241 241 236 226  15  47 &lt;BR /&gt;
host=10.142.102.50   Options|  sourcetype=Datapower   Options|  source=udp:514   Options|  Test001=pl-wlmuatdp4   Options&lt;/P&gt;

&lt;P&gt;We want to filter the data based on the field "in01_sr" the field has 4 possible values.  Does anyone know how we can filter based on this value?  Would it be done on the indexers or on the heavy forwarder?  We would like to set it up so that we route to a separate index based on that value.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Aug 2013 16:30:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-UDP-data-filtering-to-index/m-p/46381#M8728</guid>
      <dc:creator>mookiie2005</dc:creator>
      <dc:date>2013-08-26T16:30:15Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog UDP data filtering to index</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-UDP-data-filtering-to-index/m-p/46382#M8729</link>
      <description>&lt;P&gt;filter on the heavy forwarder if you have any, otherwise on the indexer  (the instance that will be Parsing the events first)&lt;BR /&gt;
you can see this page for nullQueue examples :&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.4/Deploy/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.4/Deploy/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2013 15:11:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-UDP-data-filtering-to-index/m-p/46382#M8729</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2013-08-27T15:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog UDP data filtering to index</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-UDP-data-filtering-to-index/m-p/46383#M8730</link>
      <description>&lt;P&gt;[Datapower]&lt;BR /&gt;
TRANSFORMS-routing=st02_sr_routing&lt;BR /&gt;
TRANSFORMS-routing=in01_sr_routing&lt;BR /&gt;
TRANSFORMS-routing=pf04_sr_routing&lt;BR /&gt;
TRANSFORMS-routing=uat_sr_routing&lt;/P&gt;

&lt;P&gt;[st02_sr_routing]&lt;BR /&gt;
REGEX = st02_sr&lt;BR /&gt;
DEST_KEY=_MetaData:Index&lt;BR /&gt;
FORMAT=Datapower_SIT&lt;/P&gt;

&lt;P&gt;[in01_sr_routing]&lt;BR /&gt;
REGEX = in01_sr&lt;BR /&gt;
DEST_KEY=_MetaData:Index&lt;BR /&gt;
FORMAT=Datapower_INT&lt;/P&gt;

&lt;P&gt;[pf04_sr_routing]&lt;BR /&gt;
REGEX = pf04_sr&lt;BR /&gt;
DEST_KEY=_MetaData:Index&lt;BR /&gt;
FORMAT=Datapower_Perf&lt;/P&gt;

&lt;P&gt;[uat_sr_routing]&lt;BR /&gt;
REGEX = uat_sr&lt;BR /&gt;
DEST_KEY=_MetaData:Index&lt;BR /&gt;
FORMAT=Datapower_uat&lt;/P&gt;

&lt;P&gt;the above stanzas worked for what we were trying to do.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:39:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-UDP-data-filtering-to-index/m-p/46383#M8730</guid>
      <dc:creator>mookiie2005</dc:creator>
      <dc:date>2020-09-28T14:39:50Z</dc:date>
    </item>
  </channel>
</rss>

