<?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 Having trouble with log filtering in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Having-trouble-with-log-filtering/m-p/94054#M19573</link>
    <description>&lt;P&gt;I am running into trouble with filtering logs before they are handed off to the indexer. Right now, my setup is that a I am co-hosting an &lt;CODE&gt;rsyslog&lt;/CODE&gt; daemon on the same box that holds Splunk. The reason for that is that I want to retain all original logs coming in via syslog, but only a subset should go into Splunk. &lt;/P&gt;

&lt;P&gt;My concept was that I have the syslogs deposited in a directory and have Splunk monitor that. Using &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.1.5/Admin/Routeandfilterdata#Keep_specific_events_and_discard_the_rest"&gt;these instructions&lt;/A&gt;, I set up &lt;CODE&gt;props.conf&lt;/CODE&gt; and &lt;CODE&gt;transforms.conf&lt;/CODE&gt; as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# cat props.conf
[source::/var/log/remote/log1.log]
TRANSFORMS-wireless = setnull,setparsing

# cat transforms.conf
[setnull]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[setparsing]
REGEX = Assoc success|User Authentication
DEST_KEY = queue
FORMAT = indexQueue
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, when I activate the log file, data starts pouring into Splunk, without filtering, and quickly running through my license. I did run an &lt;CODE&gt;"|extract reload=true"&lt;/CODE&gt; search to make sure that the new configurations were loaded before I tested.&lt;/P&gt;

&lt;P&gt;The regular expression appears to be correct, as confirmed by a quick &lt;CODE&gt;grep -E&lt;/CODE&gt; on the file.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Oct 2012 01:07:51 GMT</pubDate>
    <dc:creator>leune</dc:creator>
    <dc:date>2012-10-18T01:07:51Z</dc:date>
    <item>
      <title>Having trouble with log filtering</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Having-trouble-with-log-filtering/m-p/94054#M19573</link>
      <description>&lt;P&gt;I am running into trouble with filtering logs before they are handed off to the indexer. Right now, my setup is that a I am co-hosting an &lt;CODE&gt;rsyslog&lt;/CODE&gt; daemon on the same box that holds Splunk. The reason for that is that I want to retain all original logs coming in via syslog, but only a subset should go into Splunk. &lt;/P&gt;

&lt;P&gt;My concept was that I have the syslogs deposited in a directory and have Splunk monitor that. Using &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.1.5/Admin/Routeandfilterdata#Keep_specific_events_and_discard_the_rest"&gt;these instructions&lt;/A&gt;, I set up &lt;CODE&gt;props.conf&lt;/CODE&gt; and &lt;CODE&gt;transforms.conf&lt;/CODE&gt; as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# cat props.conf
[source::/var/log/remote/log1.log]
TRANSFORMS-wireless = setnull,setparsing

# cat transforms.conf
[setnull]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[setparsing]
REGEX = Assoc success|User Authentication
DEST_KEY = queue
FORMAT = indexQueue
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, when I activate the log file, data starts pouring into Splunk, without filtering, and quickly running through my license. I did run an &lt;CODE&gt;"|extract reload=true"&lt;/CODE&gt; search to make sure that the new configurations were loaded before I tested.&lt;/P&gt;

&lt;P&gt;The regular expression appears to be correct, as confirmed by a quick &lt;CODE&gt;grep -E&lt;/CODE&gt; on the file.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2012 01:07:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Having-trouble-with-log-filtering/m-p/94054#M19573</guid>
      <dc:creator>leune</dc:creator>
      <dc:date>2012-10-18T01:07:51Z</dc:date>
    </item>
    <item>
      <title>Re: Having trouble with log filtering</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Having-trouble-with-log-filtering/m-p/94055#M19574</link>
      <description>&lt;P&gt;&lt;CODE&gt;| extract reload=true&lt;/CODE&gt; is not valid for reloading index-time settings - and in fact, as far as I know it's not needed for reloading search-time settings nowadays either, so I doubt there is ever a situation now when running &lt;CODE&gt;| extract reload=true&lt;/CODE&gt; changes anything.&lt;/P&gt;

&lt;P&gt;To activate changes that you've made to index-time settings, you need to restart Splunk.&lt;/P&gt;

&lt;P&gt;Also you're saying that you want to perform filtering before logs are handed off to the indexer. Does this mean you're attempting to perform this filtering on a forwarder of some kind? Light forwarders (such as the Universal Forwarder, or a Light Forwarder) do not perform this kind of filtering - it needs to go on the indexer.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2012 07:04:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Having-trouble-with-log-filtering/m-p/94055#M19574</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-10-18T07:04:27Z</dc:date>
    </item>
    <item>
      <title>Re: Having trouble with log filtering</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Having-trouble-with-log-filtering/m-p/94056#M19575</link>
      <description>&lt;P&gt;Thank you for the feedback; the online documentation could do with some improvement on this one &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; The help pages for &lt;CODE&gt;props.conf&lt;/CODE&gt; mention in several places that an &lt;CODE&gt;|extract reload=T&lt;/CODE&gt; should work. Restarting Splunk did indeed do the trick.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2012 20:03:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Having-trouble-with-log-filtering/m-p/94056#M19575</guid>
      <dc:creator>leune</dc:creator>
      <dc:date>2012-10-18T20:03:44Z</dc:date>
    </item>
  </channel>
</rss>

