<?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 Restrict data to be indexed in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Restrict-data-to-be-indexed/m-p/24735#M438</link>
    <description>&lt;P&gt;Hi, Im looking to find a remedy to restict the data that is being indexed by splunk to just error messages. The reason being is the data being indexed by a particular host is exceeding what my license allows. I believe there are particular config files that can be modified to do this?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jun 2011 11:13:44 GMT</pubDate>
    <dc:creator>nrelihan</dc:creator>
    <dc:date>2011-06-08T11:13:44Z</dc:date>
    <item>
      <title>Restrict data to be indexed</title>
      <link>https://community.splunk.com/t5/Installation/Restrict-data-to-be-indexed/m-p/24735#M438</link>
      <description>&lt;P&gt;Hi, Im looking to find a remedy to restict the data that is being indexed by splunk to just error messages. The reason being is the data being indexed by a particular host is exceeding what my license allows. I believe there are particular config files that can be modified to do this?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2011 11:13:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Restrict-data-to-be-indexed/m-p/24735#M438</guid>
      <dc:creator>nrelihan</dc:creator>
      <dc:date>2011-06-08T11:13:44Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict data to be indexed</title>
      <link>https://community.splunk.com/t5/Installation/Restrict-data-to-be-indexed/m-p/24736#M439</link>
      <description>&lt;P&gt;nrelihan,&lt;/P&gt;

&lt;P&gt;What you are looking for is the nullQueue in Splunk.  Essentially you use your parsing configs to determine what events should be deleted or preserved, depending on your situation.&lt;/P&gt;

&lt;P&gt;You can find &lt;A href="http://www.splunk.com/base/Documentation/4.2.1/Deploy/Routeandfilterdatad#Filter_event_data_and_send_to_queues"&gt;instructions&lt;/A&gt; in the docs, and there are many answers already &lt;A href="http://splunk-base.splunk.com/search/?q=nullQueue"&gt;posted&lt;/A&gt; that might address your specific needs.&lt;/P&gt;

&lt;P&gt;Sean&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2011 11:32:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Restrict-data-to-be-indexed/m-p/24736#M439</guid>
      <dc:creator>sdwilkerson</dc:creator>
      <dc:date>2011-06-08T11:32:04Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict data to be indexed</title>
      <link>https://community.splunk.com/t5/Installation/Restrict-data-to-be-indexed/m-p/24737#M440</link>
      <description>&lt;P&gt;Thats great Sean, exactly what I'm looking for, I'll have to do a bit of reading to wrap my head around it. thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2011 13:27:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Restrict-data-to-be-indexed/m-p/24737#M440</guid>
      <dc:creator>nrelihan</dc:creator>
      <dc:date>2011-06-08T13:27:22Z</dc:date>
    </item>
  </channel>
</rss>

