<?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 Splunk Tailing Errors in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Tailing-Errors/m-p/97168#M182572</link>
    <description>&lt;P&gt;ok, my sources use syntax like \dir\dir\...\log so that it recursively finds all of my log files.&lt;/P&gt;

&lt;P&gt;but now i see this in Splunk errors report (splunk v4.3.1 for linux)&lt;/P&gt;

&lt;P&gt;03-19-2012 13:11:32.755 -0400 ERROR TailingProcessor - matching /logs/syslog/ironports/hostA/2012/03/ against ^/logs/syslog/ironports/.*/log$&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;so why the tailing error? kinda a silly event as it gives no info as to what the error was.&lt;/LI&gt;
&lt;LI&gt;why does this report show a modified regex for the dir path? me personally, i dont like configs to look like one thing in one place and something else in another place. so instead of using ... in my source paths i should use .* ?? (question marks to indicate this is a question, etc)&lt;/LI&gt;
&lt;/OL&gt;</description>
    <pubDate>Tue, 20 Mar 2012 13:26:46 GMT</pubDate>
    <dc:creator>cvajs</dc:creator>
    <dc:date>2012-03-20T13:26:46Z</dc:date>
    <item>
      <title>Splunk Tailing Errors</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Tailing-Errors/m-p/97168#M182572</link>
      <description>&lt;P&gt;ok, my sources use syntax like \dir\dir\...\log so that it recursively finds all of my log files.&lt;/P&gt;

&lt;P&gt;but now i see this in Splunk errors report (splunk v4.3.1 for linux)&lt;/P&gt;

&lt;P&gt;03-19-2012 13:11:32.755 -0400 ERROR TailingProcessor - matching /logs/syslog/ironports/hostA/2012/03/ against ^/logs/syslog/ironports/.*/log$&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;so why the tailing error? kinda a silly event as it gives no info as to what the error was.&lt;/LI&gt;
&lt;LI&gt;why does this report show a modified regex for the dir path? me personally, i dont like configs to look like one thing in one place and something else in another place. so instead of using ... in my source paths i should use .* ?? (question marks to indicate this is a question, etc)&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Tue, 20 Mar 2012 13:26:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Tailing-Errors/m-p/97168#M182572</guid>
      <dc:creator>cvajs</dc:creator>
      <dc:date>2012-03-20T13:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Tailing Errors</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-Tailing-Errors/m-p/97169#M182573</link>
      <description>&lt;P&gt;The reason for the second one is that Splunk uses PCRE internally to implement the filters. The log message reflects the regex as used internally.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Mar 2012 14:09:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-Tailing-Errors/m-p/97169#M182573</guid>
      <dc:creator>dart</dc:creator>
      <dc:date>2012-03-20T14:09:41Z</dc:date>
    </item>
  </channel>
</rss>

