<?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: Applying NullQueue REGEX to ALL sources in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Applying-NullQueue-REGEX-to-ALL-sources/m-p/54442#M10537</link>
    <description>&lt;P&gt;If this is really what you want to do, you can put it under the &lt;CODE&gt;[default]&lt;/CODE&gt; stanza in &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/props.conf&lt;/CODE&gt;.  This should cause your TRANSFORMS rule to fire for everything.&lt;/P&gt;

&lt;P&gt;I am concerned it could wind up being overzealous, though.  If your regex matches on just the word "DEBUG", it has a lot of chances for false positives and will also hit Splunk's &lt;CODE&gt;_internal&lt;/CODE&gt; index.  Before doing this in production, test test test... &lt;/P&gt;</description>
    <pubDate>Thu, 19 Jan 2012 12:14:39 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2012-01-19T12:14:39Z</dc:date>
    <item>
      <title>Applying NullQueue REGEX to ALL sources</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Applying-NullQueue-REGEX-to-ALL-sources/m-p/54441#M10536</link>
      <description>&lt;P&gt;Hi Guys - &lt;/P&gt;

&lt;P&gt;I'm trying to remove "DEBUG" messages from ALL inputs. What do I put in props.conf to apply a transform to all incoming data - or am I going about this wrong?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;BR /&gt;
-Mike&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2012 09:14:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Applying-NullQueue-REGEX-to-ALL-sources/m-p/54441#M10536</guid>
      <dc:creator>tewner</dc:creator>
      <dc:date>2012-01-19T09:14:00Z</dc:date>
    </item>
    <item>
      <title>Re: Applying NullQueue REGEX to ALL sources</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Applying-NullQueue-REGEX-to-ALL-sources/m-p/54442#M10537</link>
      <description>&lt;P&gt;If this is really what you want to do, you can put it under the &lt;CODE&gt;[default]&lt;/CODE&gt; stanza in &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/props.conf&lt;/CODE&gt;.  This should cause your TRANSFORMS rule to fire for everything.&lt;/P&gt;

&lt;P&gt;I am concerned it could wind up being overzealous, though.  If your regex matches on just the word "DEBUG", it has a lot of chances for false positives and will also hit Splunk's &lt;CODE&gt;_internal&lt;/CODE&gt; index.  Before doing this in production, test test test... &lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2012 12:14:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Applying-NullQueue-REGEX-to-ALL-sources/m-p/54442#M10537</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-01-19T12:14:39Z</dc:date>
    </item>
    <item>
      <title>Re: Applying NullQueue REGEX to ALL sources</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Applying-NullQueue-REGEX-to-ALL-sources/m-p/54443#M10538</link>
      <description>&lt;P&gt;Thanks!!!!&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2012 12:18:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Applying-NullQueue-REGEX-to-ALL-sources/m-p/54443#M10538</guid>
      <dc:creator>tewner</dc:creator>
      <dc:date>2012-01-19T12:18:39Z</dc:date>
    </item>
  </channel>
</rss>

