<?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: Help with wildcard inputs issues in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146761#M29892</link>
    <description>&lt;P&gt;Thank you, this is fantastic.  I'm noticing that the splunkd is recommending that I set a crcsalt setting, because the error log is small.  In this case, since they are all using the same inputs stanza, how would I do that?  &lt;/P&gt;</description>
    <pubDate>Mon, 08 Dec 2014 12:22:09 GMT</pubDate>
    <dc:creator>a212830</dc:creator>
    <dc:date>2014-12-08T12:22:09Z</dc:date>
    <item>
      <title>Help with wildcard inputs issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146757#M29888</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have some new inputs configured with wildcards and whitelists, but they aren't pulling in the data.  &lt;/P&gt;

&lt;P&gt;The path to the files is:  /xt112qdal0/log/app/XTRAC/6.9.1.1/XTRAC6.9.1.1_ClusterMbr1/xtrac.error.log&lt;/P&gt;

&lt;P&gt;(Note that this paticular file can exist in many different sub-directories off the ..log parent, hence the wildcard)&lt;/P&gt;

&lt;P&gt;I've confirmed that the filed is readable.  I can see the connection being made to the indexer, so, I'm assuming that it's my inputs:&lt;/P&gt;

&lt;P&gt;[monitor:///xt*qa*/log/]&lt;BR /&gt;
recursive = Yes&lt;BR /&gt;
index = Xtrac_ceops_qa_pm_logs&lt;BR /&gt;
sourcetype = xtrac_error&lt;BR /&gt;
followTail = 0&lt;BR /&gt;
disabled = 0&lt;BR /&gt;
whitelist = xtrac.error.log&lt;BR /&gt;
crcSalt = &lt;/P&gt;

&lt;P&gt;Is something wrong with this setup?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 18:20:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146757#M29888</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2020-09-28T18:20:24Z</dc:date>
    </item>
    <item>
      <title>Re: Help with wildcard inputs issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146758#M29889</link>
      <description>&lt;P&gt;Try this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///xt*qa*/log/]
index = Xtrac_ceops_qa_pm_logs
sourcetype = xtrac_error
whitelist = xtrac.error.log
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You don't need most of the settings, as you are using the defaults. Plus &lt;CODE&gt;recursive = Yes&lt;/CODE&gt; is not a valid setting.&lt;/P&gt;

&lt;P&gt;Finally, in your path example, the first directory name is &lt;CODE&gt;tx112qdal0&lt;/CODE&gt; and in the regular expression, you are missing the d  between the q and the a. This may be the real problem...&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2014 00:54:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146758#M29889</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-12-08T00:54:19Z</dc:date>
    </item>
    <item>
      <title>Re: Help with wildcard inputs issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146759#M29890</link>
      <description>&lt;P&gt;Thanks.  Picked up the typo, and it found one of the files(trace), but not the others, even after making your recommended changes.  The full inputs is the following:&lt;/P&gt;

&lt;P&gt;[monitor:///xt*q*/log/]&lt;BR /&gt;
index = Xtrac_ceops_qa_wf_logs&lt;BR /&gt;
sourcetype = xtrac_error&lt;BR /&gt;
whitelist = xtrac.error.log&lt;/P&gt;

&lt;P&gt;[monitor:///xt*q*/log/]&lt;BR /&gt;
index = Xtrac_ceops_qa_wf_logs&lt;BR /&gt;
sourcetype = xtrac_perf&lt;BR /&gt;
whitelist = xtrac.perf.log&lt;/P&gt;

&lt;P&gt;[monitor:///xt*q*/log/]&lt;BR /&gt;
index = Xtrac_ceops_qa_wf_logs&lt;BR /&gt;
sourcetype = xtrac_trace&lt;BR /&gt;
whitelist = xtrac.trace.log&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 18:20:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146759#M29890</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2020-09-28T18:20:28Z</dc:date>
    </item>
    <item>
      <title>Re: Help with wildcard inputs issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146760#M29891</link>
      <description>&lt;P&gt;Aha - this is the problem. You cannot have multiple stanzas with the same monitor.  Do this instead:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;inputs.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///xt*q*/log/]
index = Xtrac_ceops_qa_wf_logs
whitelist = xtrac\.(error|trace|perf)\.log$
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::.../xtrac.error.log]
sourcetype = xtrac_error

[source::.../xtrac.perf.log]
sourcetype = xtrac_perf

[source::.../xtrac.trace.log]
sourcetype = xtrac_trace
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Here is a reference in the &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Bypassautomaticsourcetypeassignment#Specify_source_type_for_a_source"&gt;Getting Data In&lt;/A&gt; manual for more information.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2014 07:45:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146760#M29891</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-12-08T07:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: Help with wildcard inputs issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146761#M29892</link>
      <description>&lt;P&gt;Thank you, this is fantastic.  I'm noticing that the splunkd is recommending that I set a crcsalt setting, because the error log is small.  In this case, since they are all using the same inputs stanza, how would I do that?  &lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2014 12:22:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146761#M29892</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2014-12-08T12:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: Help with wildcard inputs issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146762#M29893</link>
      <description>&lt;P&gt;To do that, add the following line to your inputs.conf stanza:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;crcSalt=&amp;lt;SOURCE&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This tells Splunk to consider the full path name of your file, as well as the contents of the file, to determine if a file is unique. (Splunk looks at the contents of each file to determine if it has already indexed the data.)&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2014 22:46:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146762#M29893</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-12-08T22:46:41Z</dc:date>
    </item>
    <item>
      <title>Re: Help with wildcard inputs issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146763#M29894</link>
      <description>&lt;P&gt;Thanks.  I was aware of crcSalt, but I'm never quite sure if it should be applied to all sources, or just certain ones.  &lt;/P&gt;

&lt;P&gt;That said, is this valid?  I'm going to have a lot of files for this feed, so I'm concerned that the whitelist will reach a size limit.&lt;/P&gt;

&lt;P&gt;[monitor:///xt*q*/log/]&lt;BR /&gt;
index = Xtrac_ceops_qa_wf_logs&lt;BR /&gt;
whitelist = xtrac.(error|trace|perf).log$&lt;/P&gt;

&lt;P&gt;[monitor:///xt*q*/log/]&lt;BR /&gt;
index = Xtrac_ceops_qa_wf_logs&lt;BR /&gt;
whitelist = xwb.(error|trace|perf).log$&lt;/P&gt;

&lt;P&gt;[monitor:///xt*q*/log/]&lt;BR /&gt;
index = Xtrac_ceops_qa_wf_logs&lt;BR /&gt;
whitelist = fuse.log$&lt;/P&gt;

&lt;P&gt;[monitor:///xt*q*/log/]&lt;BR /&gt;
index = Xtrac_ceops_qa_wf_logs&lt;BR /&gt;
whitelist = TimerManager.log$&lt;/P&gt;

&lt;P&gt;[monitor:///xt*q*/log/]&lt;BR /&gt;
index = Xtrac_ceops_qa_wf_logs&lt;BR /&gt;
whitelist = System(Err|Out).log$&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 18:20:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146763#M29894</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2020-09-28T18:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: Help with wildcard inputs issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146764#M29895</link>
      <description>&lt;P&gt;Wait!! You CANNOT have monitor stanzas that overlap. You have 5 identical monitor stanzas - this will not work!&lt;/P&gt;

&lt;P&gt;Don't worry about the length of the whitelist... &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///xt*q*/log/]
index = Xtrac_ceops_qa_wf_logs
whitelist = (xtrac|xwb).(error|trace|perf).log$|fuse.log$|TimeManager.log$|System(Err|Out).log$
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;is not that long. But you could add more information into the monitor stanza as well:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///xt*q*/log/.../fuse.log]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;for example.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2014 17:32:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146764#M29895</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-12-10T17:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: Help with wildcard inputs issues</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146765#M29896</link>
      <description>&lt;P&gt;Thanks - yes, I realized that wouldn't work. &lt;/P&gt;

&lt;P&gt;The whitelist could get quite large - hence my concern.  Would the example above work for a fuse.log that exists in any directory off ../log?  The number and level of subdirectories varies - could be 2, could be 5... - want to make sure it would work.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Dec 2014 14:58:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Help-with-wildcard-inputs-issues/m-p/146765#M29896</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2014-12-11T14:58:55Z</dc:date>
    </item>
  </channel>
</rss>

