<?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 TCP_ROUTING Sub-folders of monitors fails in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/TCP-ROUTING-Sub-folders-of-monitors-fails/m-p/93394#M19427</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;
Monitoring subfolders of other monitors while using TCP_ROUTING results in subfolders not being indexed.&lt;BR /&gt;
Do anyone of you have any experiences with this, or possible workarounds? &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Removing the /var/log monitor will get data into to the customer01 and customer02 servers, so i know that the ROUTING is working.&lt;/P&gt;

&lt;P&gt;Adding additional TCP_ROUTING to /var/log/ do not seem to help.&lt;/P&gt;

&lt;P&gt;[monitor:///var/log/customer]&lt;BR /&gt;
disabled=false&lt;BR /&gt;
index=index1y&lt;BR /&gt;
blacklist=.(gz|\d+)$&lt;BR /&gt;
recursive=false&lt;BR /&gt;
_TCP_ROUTING=customer01,customer02&lt;/P&gt;

&lt;P&gt;[monitor:///var/log]&lt;BR /&gt;
disabled =  false&lt;BR /&gt;
blacklist = (.(gz|bz2|z|zip)|lastlog|wtmp|btmp)$&lt;BR /&gt;
followTail = 1&lt;BR /&gt;
recursive = false&lt;/P&gt;

&lt;P&gt;--&lt;BR /&gt;
Best regards&lt;BR /&gt;
Espen&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 09:59:51 GMT</pubDate>
    <dc:creator>efo</dc:creator>
    <dc:date>2020-09-28T09:59:51Z</dc:date>
    <item>
      <title>TCP_ROUTING Sub-folders of monitors fails</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-ROUTING-Sub-folders-of-monitors-fails/m-p/93394#M19427</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
Monitoring subfolders of other monitors while using TCP_ROUTING results in subfolders not being indexed.&lt;BR /&gt;
Do anyone of you have any experiences with this, or possible workarounds? &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Removing the /var/log monitor will get data into to the customer01 and customer02 servers, so i know that the ROUTING is working.&lt;/P&gt;

&lt;P&gt;Adding additional TCP_ROUTING to /var/log/ do not seem to help.&lt;/P&gt;

&lt;P&gt;[monitor:///var/log/customer]&lt;BR /&gt;
disabled=false&lt;BR /&gt;
index=index1y&lt;BR /&gt;
blacklist=.(gz|\d+)$&lt;BR /&gt;
recursive=false&lt;BR /&gt;
_TCP_ROUTING=customer01,customer02&lt;/P&gt;

&lt;P&gt;[monitor:///var/log]&lt;BR /&gt;
disabled =  false&lt;BR /&gt;
blacklist = (.(gz|bz2|z|zip)|lastlog|wtmp|btmp)$&lt;BR /&gt;
followTail = 1&lt;BR /&gt;
recursive = false&lt;/P&gt;

&lt;P&gt;--&lt;BR /&gt;
Best regards&lt;BR /&gt;
Espen&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:59:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-ROUTING-Sub-folders-of-monitors-fails/m-p/93394#M19427</guid>
      <dc:creator>efo</dc:creator>
      <dc:date>2020-09-28T09:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: TCP_ROUTING Sub-folders of monitors fails</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-ROUTING-Sub-folders-of-monitors-fails/m-p/93395#M19428</link>
      <description>&lt;P&gt;I guess you stumbled on the same "bug" as I did.&lt;BR /&gt;
This was my workaround:&lt;BR /&gt;
&lt;A href="http://answers.splunk.com/answers/126064/bug-in-universal-forwarder-inputsconf-monitor-and-recursive-false/126243"&gt;http://answers.splunk.com/answers/126064/bug-in-universal-forwarder-inputsconf-monitor-and-recursive-false/126243&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2014 18:09:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-ROUTING-Sub-folders-of-monitors-fails/m-p/93395#M19428</guid>
      <dc:creator>elof</dc:creator>
      <dc:date>2014-03-10T18:09:17Z</dc:date>
    </item>
  </channel>
</rss>

