<?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: fschange filters for windows in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/fschange-filters-for-windows/m-p/17509#M2274</link>
    <description>&lt;P&gt;Looks like your regex is incorrect.  Try using the filter:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[filter:blacklist:pamping]
regex1 = .*ignore.*
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Or, for your origional path:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[filter:blacklist:pamping]
regex1 = c:\\pamping\\ignore\\.*
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Keep in mind that when you are writting a regex, you have to use "\\" to match a single "\".  And you have to use ".*" to mean match any character 0 or more times.&lt;/P&gt;

&lt;P&gt;Your origional regex of "&lt;CODE&gt;\*\ignore\*&lt;/CODE&gt;" is literally interpreted as match a literal "&lt;CODE&gt;*&lt;/CODE&gt;" followed by  an "&lt;CODE&gt;i&lt;/CODE&gt;" (I don't think that "&lt;CODE&gt;\i&lt;/CODE&gt;" means anything in regex speak, so this is my best guess) followed by &lt;CODE&gt;gnore&lt;/CODE&gt; followed by a literal "&lt;CODE&gt;*&lt;/CODE&gt;"; which isn't at all what you want.  For a general regex introduction and other helpful resources, check out:  &lt;A href="http://www.regular-expressions.info/" rel="nofollow"&gt;http://www.regular-expressions.info/&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 16 Jul 2010 20:17:31 GMT</pubDate>
    <dc:creator>Lowell</dc:creator>
    <dc:date>2010-07-16T20:17:31Z</dc:date>
    <item>
      <title>fschange filters for windows</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/fschange-filters-for-windows/m-p/17508#M2273</link>
      <description>&lt;P&gt;I tried searching for documentation on how to implement 
filters for directories ( in fschange)&lt;/P&gt;

&lt;P&gt;Could someone let me know where could I find documentation on this? the documentation page has an example to blacklist all the contents within a directory, how about a particular directory?&lt;/P&gt;

&lt;P&gt;Here is my windows fschange implementation&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[filter:blacklist:pamping]
regex1=\*\ignore\* ( tried c:\pamping\ignore\* didnt work)

[fschange:c:\pamping]
index = _audit
sourcetype = fschange
signedaudit = false
sendEventMaxSize = -1
recurse = true
disabled = false
pollPeriod = 60
filesPerDelay = 10
delayInMills = 100
followLinks = false
fullEvent = false
filters=pamping
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The above filter which was set wasnt filtering events within the ignore directory, am i applying the filter incorrectly?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2010 16:11:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/fschange-filters-for-windows/m-p/17508#M2273</guid>
      <dc:creator>heterodyned</dc:creator>
      <dc:date>2010-07-16T16:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: fschange filters for windows</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/fschange-filters-for-windows/m-p/17509#M2274</link>
      <description>&lt;P&gt;Looks like your regex is incorrect.  Try using the filter:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[filter:blacklist:pamping]
regex1 = .*ignore.*
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Or, for your origional path:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[filter:blacklist:pamping]
regex1 = c:\\pamping\\ignore\\.*
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Keep in mind that when you are writting a regex, you have to use "\\" to match a single "\".  And you have to use ".*" to mean match any character 0 or more times.&lt;/P&gt;

&lt;P&gt;Your origional regex of "&lt;CODE&gt;\*\ignore\*&lt;/CODE&gt;" is literally interpreted as match a literal "&lt;CODE&gt;*&lt;/CODE&gt;" followed by  an "&lt;CODE&gt;i&lt;/CODE&gt;" (I don't think that "&lt;CODE&gt;\i&lt;/CODE&gt;" means anything in regex speak, so this is my best guess) followed by &lt;CODE&gt;gnore&lt;/CODE&gt; followed by a literal "&lt;CODE&gt;*&lt;/CODE&gt;"; which isn't at all what you want.  For a general regex introduction and other helpful resources, check out:  &lt;A href="http://www.regular-expressions.info/" rel="nofollow"&gt;http://www.regular-expressions.info/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2010 20:17:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/fschange-filters-for-windows/m-p/17509#M2274</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2010-07-16T20:17:31Z</dc:date>
    </item>
    <item>
      <title>Re: fschange filters for windows</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/fschange-filters-for-windows/m-p/17510#M2275</link>
      <description>&lt;P&gt;Thank you so much, is this format specifically for windowS? or would it apply for Linux as well? For Linux I generally use the format&lt;BR /&gt;
/Folder/Subfolder/* format, and it generally filters the data, but does a strange delete-parent, delete etc...&lt;/P&gt;</description>
      <pubDate>Sat, 17 Jul 2010 11:39:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/fschange-filters-for-windows/m-p/17510#M2275</guid>
      <dc:creator>heterodyned</dc:creator>
      <dc:date>2010-07-17T11:39:54Z</dc:date>
    </item>
    <item>
      <title>Re: fschange filters for windows</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/fschange-filters-for-windows/m-p/17511#M2276</link>
      <description>&lt;P&gt;Yeah.  You can use either a literal forward slash like "/", or if you are writing rules that can be used on either location, then I use &lt;CODE&gt;[/\\]&lt;/CODE&gt; which will match a single forwarder slash for unix, or a backslash for windows.  As far as the delete parent stuff, I don't full get how that works myself.  If you keep getting them after your initial filter change, then I would suggest posting another question about it.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jul 2010 20:20:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/fschange-filters-for-windows/m-p/17511#M2276</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2010-07-19T20:20:46Z</dc:date>
    </item>
  </channel>
</rss>

