<?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: Monitor doesn't work with the path including a space character in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Monitor-doesn-t-work-with-the-path-including-a-space-character/m-p/21663#M3264</link>
    <description>&lt;P&gt;Thank you for your help, Mr. Takjian.&lt;/P&gt;

&lt;P&gt;I'd been confused about "source" display of splunk.&lt;BR /&gt;
I wondered "source" was less than monitor files.&lt;/P&gt;

&lt;P&gt;But the monitor files had duplicated contents. Same lines were recorded on files in different directories. &lt;BR /&gt;
Then the "source" was less than monitor files.&lt;/P&gt;

&lt;P&gt;It seems that there is no lack of file contents.&lt;/P&gt;

&lt;P&gt;I'm sorry about my confusion. &lt;/P&gt;</description>
    <pubDate>Wed, 01 Aug 2012 01:47:48 GMT</pubDate>
    <dc:creator>hi_sekine</dc:creator>
    <dc:date>2012-08-01T01:47:48Z</dc:date>
    <item>
      <title>Monitor doesn't work with the path including a space character</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Monitor-doesn-t-work-with-the-path-including-a-space-character/m-p/21661#M3262</link>
      <description>&lt;P&gt;Is there any workaround ?&lt;/P&gt;

&lt;P&gt;I have logs that path beginning with space character. But Splunk doesn't detect them.&lt;/P&gt;

&lt;P&gt;Sample files:&lt;BR /&gt;
Log\20120711\ 0313139\Name54detail.log&lt;BR /&gt;
Log\20120711\ 1281020\Name55detail.log&lt;/P&gt;

&lt;P&gt;inputs.conf:&lt;BR /&gt;
[monitor://E:\user05...Nam*[Dd]etai*.[Ll][Oo][Gg]]&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 12:10:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Monitor-doesn-t-work-with-the-path-including-a-space-character/m-p/21661#M3262</guid>
      <dc:creator>hi_sekine</dc:creator>
      <dc:date>2020-09-28T12:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor doesn't work with the path including a space character</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Monitor-doesn-t-work-with-the-path-including-a-space-character/m-p/21662#M3263</link>
      <description>&lt;P&gt;I think you can use whitelist. Can you try following configuration?&lt;/P&gt;

&lt;P&gt;[monitor:///user05.../]&lt;BR /&gt;
whitelist = Nam[^/]*.log$&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jul 2012 06:05:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Monitor-doesn-t-work-with-the-path-including-a-space-character/m-p/21662#M3263</guid>
      <dc:creator>Takajian</dc:creator>
      <dc:date>2012-07-31T06:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor doesn't work with the path including a space character</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Monitor-doesn-t-work-with-the-path-including-a-space-character/m-p/21663#M3264</link>
      <description>&lt;P&gt;Thank you for your help, Mr. Takjian.&lt;/P&gt;

&lt;P&gt;I'd been confused about "source" display of splunk.&lt;BR /&gt;
I wondered "source" was less than monitor files.&lt;/P&gt;

&lt;P&gt;But the monitor files had duplicated contents. Same lines were recorded on files in different directories. &lt;BR /&gt;
Then the "source" was less than monitor files.&lt;/P&gt;

&lt;P&gt;It seems that there is no lack of file contents.&lt;/P&gt;

&lt;P&gt;I'm sorry about my confusion. &lt;/P&gt;</description>
      <pubDate>Wed, 01 Aug 2012 01:47:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Monitor-doesn-t-work-with-the-path-including-a-space-character/m-p/21663#M3264</guid>
      <dc:creator>hi_sekine</dc:creator>
      <dc:date>2012-08-01T01:47:48Z</dc:date>
    </item>
  </channel>
</rss>

