<?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: Filter _internal events that get forwarded in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Filter-internal-events-that-get-forwarded/m-p/182023#M36476</link>
    <description>&lt;P&gt;Perhaps this can be of help? Either stop forwarding the &lt;CODE&gt;_internal&lt;/CODE&gt; events from the forwarders altogether with the &lt;CODE&gt;forwardedindex&lt;/CODE&gt; setting in outputs.conf, or configure the logging levels for the various components through log.cfg;&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/outputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/outputsconf&lt;/A&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.1/Troubleshooting/WhatSplunklogsaboutitself"&gt;http://docs.splunk.com/Documentation/Splunk/6.0.1/Troubleshooting/WhatSplunklogsaboutitself&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Dec 2013 23:22:40 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2013-12-17T23:22:40Z</dc:date>
    <item>
      <title>Filter _internal events that get forwarded</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Filter-internal-events-that-get-forwarded/m-p/182022#M36475</link>
      <description>&lt;P&gt;My company has a lot of small, independent offices that have a handful of machines in each locations.  The problem is there are literally hundreds of locations, many of them rural with low bandwidth.&lt;/P&gt;

&lt;P&gt;I'd like to filter what gets sent to index=_internal by the UniversalForwarder.  I know that a Heavy forwarder can do that, but I've already provisioned thousands of Windows machines with Splunk and the _internal index is clogging some of the pipes.  Any suggestion how to get just warnings and alerts for _internal instead of bandwidth-filling info events?&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2013 21:28:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Filter-internal-events-that-get-forwarded/m-p/182022#M36475</guid>
      <dc:creator>belka</dc:creator>
      <dc:date>2013-12-17T21:28:41Z</dc:date>
    </item>
    <item>
      <title>Re: Filter _internal events that get forwarded</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Filter-internal-events-that-get-forwarded/m-p/182023#M36476</link>
      <description>&lt;P&gt;Perhaps this can be of help? Either stop forwarding the &lt;CODE&gt;_internal&lt;/CODE&gt; events from the forwarders altogether with the &lt;CODE&gt;forwardedindex&lt;/CODE&gt; setting in outputs.conf, or configure the logging levels for the various components through log.cfg;&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/outputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/outputsconf&lt;/A&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.1/Troubleshooting/WhatSplunklogsaboutitself"&gt;http://docs.splunk.com/Documentation/Splunk/6.0.1/Troubleshooting/WhatSplunklogsaboutitself&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2013 23:22:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Filter-internal-events-that-get-forwarded/m-p/182023#M36476</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-12-17T23:22:40Z</dc:date>
    </item>
  </channel>
</rss>

