<?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: Minimize Size of Logs being processed?? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Minimize-Size-of-Logs-being-processed/m-p/39015#M7225</link>
    <description>&lt;P&gt;Ok. So I will assume you are monitoring entire directories at the moment and pulling all logs in.&lt;BR /&gt;
There is something called a nullQueue in splunk, when an event arrives it goes through several stages of parsing and queues before eventually being indexed. Just before it arrives at the index you can filter off certain events into a "nullQueue". These do not get indexed and simply get written away.&lt;/P&gt;

&lt;P&gt;Have a read of;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Routeandfilterdatad#Filter_event_data_and_send_to_queues" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Routeandfilterdatad#Filter_event_data_and_send_to_queues&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If you have any problems then just update your question with anything you've tried and the community can help troubleshoot it further.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 10:14:36 GMT</pubDate>
    <dc:creator>Drainy</dc:creator>
    <dc:date>2020-09-28T10:14:36Z</dc:date>
    <item>
      <title>Minimize Size of Logs being processed??</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Minimize-Size-of-Logs-being-processed/m-p/39014#M7224</link>
      <description>&lt;P&gt;I have splunk free installed and want to log some remote server but the Security Log is hogging my 500MB daily allowance I am using remote agents, is there a way to only index aspects of the security Log in splunk? Obviously I don't at the moment care about succesful logins and log outs ets&lt;/P&gt;</description>
      <pubDate>Thu, 22 Dec 2011 09:35:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Minimize-Size-of-Logs-being-processed/m-p/39014#M7224</guid>
      <dc:creator>stevehoweuk</dc:creator>
      <dc:date>2011-12-22T09:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: Minimize Size of Logs being processed??</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Minimize-Size-of-Logs-being-processed/m-p/39015#M7225</link>
      <description>&lt;P&gt;Ok. So I will assume you are monitoring entire directories at the moment and pulling all logs in.&lt;BR /&gt;
There is something called a nullQueue in splunk, when an event arrives it goes through several stages of parsing and queues before eventually being indexed. Just before it arrives at the index you can filter off certain events into a "nullQueue". These do not get indexed and simply get written away.&lt;/P&gt;

&lt;P&gt;Have a read of;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Routeandfilterdatad#Filter_event_data_and_send_to_queues" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Routeandfilterdatad#Filter_event_data_and_send_to_queues&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If you have any problems then just update your question with anything you've tried and the community can help troubleshoot it further.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 10:14:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Minimize-Size-of-Logs-being-processed/m-p/39015#M7225</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2020-09-28T10:14:36Z</dc:date>
    </item>
  </channel>
</rss>

