<?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 Deployment app wildcard Issue with inputs.conf file on windows application in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-app-wildcard-Issue-with-inputs-conf-file-on-windows/m-p/258526#M49649</link>
    <description>&lt;P&gt;We have multiple forwarders running on Windows servers that need to monitor application log directories. The only difference in each log path, is one segment.&lt;/P&gt;

&lt;P&gt;For Example:&lt;/P&gt;

&lt;P&gt;D:\abc\tra\domain\CPWCLPRD\application\logs\&lt;BR /&gt;
D:\abc\tra\domain\CPWULPRD\application\logs\&lt;BR /&gt;
D:\abc\tra\domain\SSSCQA\application\logs\&lt;/P&gt;

&lt;P&gt;When the path is explicitly defined, the monitor works. However, I have been trying to use the following monitor in the inputs.conf file, but it doesn't work as soon as I put the "..." wildcard in.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://D:\abc\tra\domain\\...\application\logs\]
disabled = false
ignoreOlderThan = 7d
sourcetype = abc_defghi
index = xyz_funding
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 30 Nov 2016 14:58:40 GMT</pubDate>
    <dc:creator>rcrook89</dc:creator>
    <dc:date>2016-11-30T14:58:40Z</dc:date>
    <item>
      <title>Deployment app wildcard Issue with inputs.conf file on windows application</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-app-wildcard-Issue-with-inputs-conf-file-on-windows/m-p/258526#M49649</link>
      <description>&lt;P&gt;We have multiple forwarders running on Windows servers that need to monitor application log directories. The only difference in each log path, is one segment.&lt;/P&gt;

&lt;P&gt;For Example:&lt;/P&gt;

&lt;P&gt;D:\abc\tra\domain\CPWCLPRD\application\logs\&lt;BR /&gt;
D:\abc\tra\domain\CPWULPRD\application\logs\&lt;BR /&gt;
D:\abc\tra\domain\SSSCQA\application\logs\&lt;/P&gt;

&lt;P&gt;When the path is explicitly defined, the monitor works. However, I have been trying to use the following monitor in the inputs.conf file, but it doesn't work as soon as I put the "..." wildcard in.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://D:\abc\tra\domain\\...\application\logs\]
disabled = false
ignoreOlderThan = 7d
sourcetype = abc_defghi
index = xyz_funding
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 30 Nov 2016 14:58:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Deployment-app-wildcard-Issue-with-inputs-conf-file-on-windows/m-p/258526#M49649</guid>
      <dc:creator>rcrook89</dc:creator>
      <dc:date>2016-11-30T14:58:40Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment app wildcard Issue with inputs.conf file on windows application</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-app-wildcard-Issue-with-inputs-conf-file-on-windows/m-p/258527#M49650</link>
      <description>&lt;P&gt;I figured out the resolution on this. &lt;/P&gt;

&lt;P&gt;It looks like a bug was fixed in 6.5.1. that resolves an issue with using wildcards in the file monitor for an inputs.conf file.&lt;/P&gt;

&lt;P&gt;In 6.5, for windows, you have to specify ".." as the wildcard in an inputs.conf monitor. &lt;/P&gt;

&lt;P&gt;In 6.5.1, for windows, you can specify "..." in an inputs.conf file as the wildcard (per Splunk's documentation).&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2016 22:42:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Deployment-app-wildcard-Issue-with-inputs-conf-file-on-windows/m-p/258527#M49650</guid>
      <dc:creator>rcrook89</dc:creator>
      <dc:date>2016-11-30T22:42:06Z</dc:date>
    </item>
  </channel>
</rss>

