<?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 Inputs hierarchy in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-hierarchy/m-p/353667#M64736</link>
    <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I want to monitor a directory but within that directory is another directory which I want to index under a different Source Type.&lt;/P&gt;

&lt;P&gt;specifcally:&lt;BR /&gt;
[monitor:///var/log/*]&lt;BR /&gt;
sourcetype syslog&lt;/P&gt;

&lt;P&gt;and the subfolder&lt;BR /&gt;
&lt;A href="https://community.splunk.com/which%20contains%20apache%20access%20logs"&gt;monitor:///var/log/apache2/*&lt;/A&gt;&lt;BR /&gt;
sourcetype apache_error&lt;/P&gt;

&lt;P&gt;But the second input falls under the first, and since data isn't indexed twice, I'm wondering how splunk is going to handle this.&lt;BR /&gt;
Will it just index the apache logs with the first rule with sourcetype syslog. Or is splunk smart enough to index the apache logs with the sourcetype apache_error if i define the second input like that.&lt;BR /&gt;
Or do I put the apache data input before the other one?&lt;BR /&gt;
Or do I blacklist the folder in the first input rule, if so, how?&lt;/P&gt;</description>
    <pubDate>Tue, 07 Nov 2017 10:38:03 GMT</pubDate>
    <dc:creator>fdesterke</dc:creator>
    <dc:date>2017-11-07T10:38:03Z</dc:date>
    <item>
      <title>Inputs hierarchy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-hierarchy/m-p/353667#M64736</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I want to monitor a directory but within that directory is another directory which I want to index under a different Source Type.&lt;/P&gt;

&lt;P&gt;specifcally:&lt;BR /&gt;
[monitor:///var/log/*]&lt;BR /&gt;
sourcetype syslog&lt;/P&gt;

&lt;P&gt;and the subfolder&lt;BR /&gt;
&lt;A href="https://community.splunk.com/which%20contains%20apache%20access%20logs"&gt;monitor:///var/log/apache2/*&lt;/A&gt;&lt;BR /&gt;
sourcetype apache_error&lt;/P&gt;

&lt;P&gt;But the second input falls under the first, and since data isn't indexed twice, I'm wondering how splunk is going to handle this.&lt;BR /&gt;
Will it just index the apache logs with the first rule with sourcetype syslog. Or is splunk smart enough to index the apache logs with the sourcetype apache_error if i define the second input like that.&lt;BR /&gt;
Or do I put the apache data input before the other one?&lt;BR /&gt;
Or do I blacklist the folder in the first input rule, if so, how?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2017 10:38:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-hierarchy/m-p/353667#M64736</guid>
      <dc:creator>fdesterke</dc:creator>
      <dc:date>2017-11-07T10:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs hierarchy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-hierarchy/m-p/353668#M64737</link>
      <description>&lt;P&gt;Use a blacklist within the first stanza to avoid indexing the Apache logs as syslog.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///var/log/*]
sourcetype = syslog
# blacklist uses a regular expression, not a pattern
blacklist = (.*apache2.*)

[monitor:///var/log/apache2/*]
sourcetype = apache_error
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 07 Nov 2017 14:08:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-hierarchy/m-p/353668#M64737</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2017-11-07T14:08:11Z</dc:date>
    </item>
  </channel>
</rss>

