<?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: Multiple Whitelists in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Whitelists/m-p/292303#M55688</link>
    <description>&lt;P&gt;Thanks  very much. In fact i went for the last option. &lt;/P&gt;

&lt;P&gt;Cheers&lt;/P&gt;</description>
    <pubDate>Mon, 03 Jul 2017 22:37:03 GMT</pubDate>
    <dc:creator>robertlynch2020</dc:creator>
    <dc:date>2017-07-03T22:37:03Z</dc:date>
    <item>
      <title>Multiple Whitelists</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Whitelists/m-p/292301#M55686</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;

&lt;P&gt;I have the following two inputs in inputs.conf. They both work separably but not together.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;**Working**
[monitor:///net/dell428srv/data2/apps/mx_ox62148_191418/logs_latest_17052017-064938.../*.log]
disabled = false
host = MXTIMING_TEST1_DELL428SRV
index = mlc_live
whitelist =  mxtiming_(?&amp;lt;FULL_STRING&amp;gt;\d*_[^_]*_\d*)\.log
crcSalt = &amp;lt;SOURCE&amp;gt;
sourcetype = MX_TIMING

**Working**
[monitor:///net/dell428srv/data2/apps/mx_ox62148_191418/logs_latest_17052017-064938.../*.log]
disabled = false
host = MXTIMING_TEST1_DELL428SRV
index = mlc_live
whitelist =  mxtiming_(?&amp;lt;FULL_STRING&amp;gt;[^_]*_[^_]*_\d*_[^_]*_\d*)\.log
crcSalt = &amp;lt;SOURCE&amp;gt;
sourcetype = MX_TIMING
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When i try to add them together with a | nothing works, i have a few to add so i don't want to have to keep copying this code&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;    **NOT_WORKING**
    [monitor:///net/dell428srv/data2/apps/mx_ox62148_191418/logs_latest_17052017-064938.../*.log]
    disabled = false
    host = MXTIMING_TEST1_DELL428SRV
    index = mlc_live
    whitelist =  mxtiming_(?&amp;lt;FULL_STRING&amp;gt;\d*_[^_]*_\d*)\.log|mxtiming_(?&amp;lt;FULL_STRING&amp;gt;[^_]*_[^_]*_\d*_[^_]*_\d*)\.log
crcSalt = &amp;lt;SOURCE&amp;gt;
sourcetype = MX_TIMING
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any ideas would be great &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2017 11:42:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Whitelists/m-p/292301#M55686</guid>
      <dc:creator>robertlynch2020</dc:creator>
      <dc:date>2017-06-30T11:42:14Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple Whitelists</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Whitelists/m-p/292302#M55687</link>
      <description>&lt;P&gt;Two things. First, your regex is invalid, you define FULL_STRING twice, which is not allowed in a regex. Since you aren't using a named capture group later, just get rid of it.&lt;/P&gt;

&lt;P&gt;Second, parenthesis will be your friend. Try:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;whitelist =  (mxtiming_(\d*_[^_]*_\d*)\.log)|(mxtiming_([^_]*_[^_]*_\d*_[^_]*_\d*)\.log))
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But, you can't make it better:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;whitelist = mxtiming_((\d*_[^_]*_\d)|([^_]*_[^_]*_\d*_[^_]*_\d*))\.log
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I'm not sure why you don't just use:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;whitelist = mxtiming_.*\.log
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Which should work just as well, if you don't have a third name that uses mxtiming_*.log.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2017 12:21:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Whitelists/m-p/292302#M55687</guid>
      <dc:creator>cpetterborg</dc:creator>
      <dc:date>2017-06-30T12:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple Whitelists</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Whitelists/m-p/292303#M55688</link>
      <description>&lt;P&gt;Thanks  very much. In fact i went for the last option. &lt;/P&gt;

&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jul 2017 22:37:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Whitelists/m-p/292303#M55688</guid>
      <dc:creator>robertlynch2020</dc:creator>
      <dc:date>2017-07-03T22:37:03Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple Whitelists</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Whitelists/m-p/292304#M55689</link>
      <description>&lt;P&gt;It is the easiest and will match other file names if they happen to change any in the future. I find it best to do that simplest version whenever possible. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jul 2017 22:42:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Whitelists/m-p/292304#M55689</guid>
      <dc:creator>cpetterborg</dc:creator>
      <dc:date>2017-07-03T22:42:22Z</dc:date>
    </item>
  </channel>
</rss>

