<?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: Multiple Wildcards in inputs.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Wildcards-in-inputs-conf/m-p/93646#M19458</link>
    <description>&lt;P&gt;The simple wild cards for path are : * and ..., they are automatically replaced by regexes&lt;BR /&gt;
see &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.3/Data/Specifyinputpathswithwildcards" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.3/Data/Specifyinputpathswithwildcards&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;It is not recommended to use regexes in the path (need to start to escape any special characters, by example file.txt has to be file\.txt ), instead you can use whitelist and blacklists that can contain regexes.&lt;/P&gt;

&lt;P&gt;so with your case, &lt;BR /&gt;
[monitor:///data/logs/kim/.../*MS?.log.gz]&lt;BR /&gt;
has to be something like &lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
[monitor:///data/logs/kim/...]&lt;BR /&gt;
whitelist = .*MS?\.log\.gz&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;while the second should work because it uses only wildcards.&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
[monitor:///data/logs/kim/.../&lt;EM&gt;stderr&lt;/EM&gt;]&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 12:02:32 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2020-09-28T12:02:32Z</dc:date>
    <item>
      <title>Multiple Wildcards in inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Wildcards-in-inputs-conf/m-p/93645#M19457</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Can I use the following expression in my inputs.conf&lt;/P&gt;

&lt;P&gt;/data/logs/kim/.../&lt;EM&gt;**MS?.log.gz&lt;/EM&gt;*&lt;/P&gt;

&lt;P&gt;Or&lt;/P&gt;

&lt;P&gt;/data/logs/kim/.../*&lt;STRONG&gt;&lt;EM&gt;stderr&lt;/EM&gt;&lt;/STRONG&gt;*&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jul 2012 08:31:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Wildcards-in-inputs-conf/m-p/93645#M19457</guid>
      <dc:creator>mkelderm</dc:creator>
      <dc:date>2012-07-09T08:31:53Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple Wildcards in inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Wildcards-in-inputs-conf/m-p/93646#M19458</link>
      <description>&lt;P&gt;The simple wild cards for path are : * and ..., they are automatically replaced by regexes&lt;BR /&gt;
see &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.3/Data/Specifyinputpathswithwildcards" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.3/Data/Specifyinputpathswithwildcards&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;It is not recommended to use regexes in the path (need to start to escape any special characters, by example file.txt has to be file\.txt ), instead you can use whitelist and blacklists that can contain regexes.&lt;/P&gt;

&lt;P&gt;so with your case, &lt;BR /&gt;
[monitor:///data/logs/kim/.../*MS?.log.gz]&lt;BR /&gt;
has to be something like &lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
[monitor:///data/logs/kim/...]&lt;BR /&gt;
whitelist = .*MS?\.log\.gz&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;while the second should work because it uses only wildcards.&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
[monitor:///data/logs/kim/.../&lt;EM&gt;stderr&lt;/EM&gt;]&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 12:02:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Wildcards-in-inputs-conf/m-p/93646#M19458</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2020-09-28T12:02:32Z</dc:date>
    </item>
  </channel>
</rss>

