<?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: Disable Sources.data in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41586#M9632</link>
    <description>&lt;P&gt;You can't.  The &lt;CODE&gt;Sources.data&lt;/CODE&gt; file is critical to Splunk's operation - part of its use is to help Splunk at search time to select buckets that may be relevant to a search.  (If you did a search on &lt;CODE&gt;source="/var/log/httpd/access*"&lt;/CODE&gt; then Splunk could quickly determine if a particular index bucket had any matches at all by just scanning the sources list.)&lt;/P&gt;

&lt;P&gt;A better solution might be to rewrite the value of "source" using &lt;CODE&gt;props.conf&lt;/CODE&gt; and &lt;CODE&gt;transforms.conf&lt;/CODE&gt;.  You would then want to pull out the "useful information" from the filename and put it into an otherwise indexed field.  Basically, making the source somewhat less specific but still making the useful information available to you.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Dec 2011 18:32:58 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2011-12-28T18:32:58Z</dc:date>
    <item>
      <title>Disable Sources.data</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41585#M9631</link>
      <description>&lt;P&gt;There's an app we have that is writing a file per transaction, and unfortunately, part of the useful information is in the filename itself.&lt;/P&gt;

&lt;P&gt;But, the Sources.data has grown to such an extent that it is causing performance issues as it is constantly rewritten. It is currently 2.3 gigs.&lt;/P&gt;

&lt;P&gt;What's the most effective way to essentially disable Sources.data?  I have no use for it on this index.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2011 18:00:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41585#M9631</guid>
      <dc:creator>vbumgarn</dc:creator>
      <dc:date>2011-12-28T18:00:36Z</dc:date>
    </item>
    <item>
      <title>Re: Disable Sources.data</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41586#M9632</link>
      <description>&lt;P&gt;You can't.  The &lt;CODE&gt;Sources.data&lt;/CODE&gt; file is critical to Splunk's operation - part of its use is to help Splunk at search time to select buckets that may be relevant to a search.  (If you did a search on &lt;CODE&gt;source="/var/log/httpd/access*"&lt;/CODE&gt; then Splunk could quickly determine if a particular index bucket had any matches at all by just scanning the sources list.)&lt;/P&gt;

&lt;P&gt;A better solution might be to rewrite the value of "source" using &lt;CODE&gt;props.conf&lt;/CODE&gt; and &lt;CODE&gt;transforms.conf&lt;/CODE&gt;.  You would then want to pull out the "useful information" from the filename and put it into an otherwise indexed field.  Basically, making the source somewhat less specific but still making the useful information available to you.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2011 18:32:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41586#M9632</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-12-28T18:32:58Z</dc:date>
    </item>
    <item>
      <title>Re: Disable Sources.data</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41587#M9633</link>
      <description>&lt;P&gt;I was under the impression those metadata files are only used by the |metadata commands, and the actual field values needed for search are in the tsidx files.&lt;/P&gt;

&lt;P&gt;I was going down the route of copying source into orig_source and then trying to use FIELDALIAS to make it available as source, but the filenames have spaces in them, and I can't for the life of me make an indexed field work properly with spaces in the value.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2011 18:39:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41587#M9633</guid>
      <dc:creator>vbumgarn</dc:creator>
      <dc:date>2011-12-28T18:39:51Z</dc:date>
    </item>
    <item>
      <title>Re: Disable Sources.data</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41588#M9634</link>
      <description>&lt;P&gt;The eventual answer was to do a number of things...&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Create a transform to copy the source into a new field. Be sure to add to fields.conf.&lt;/LI&gt;
&lt;LI&gt;Create a transform to set source to a common string.&lt;/LI&gt;
&lt;LI&gt;Create an alias to allow searching the new field as source.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;This effectively short circuits Sources.meta. It would be nice if there was a setting in props.conf to do all of this for you. Basically, a setting that says "I still want to be able to search this field, but I don't care if it works for the metadata command."&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2011 20:30:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41588#M9634</guid>
      <dc:creator>vbumgarn</dc:creator>
      <dc:date>2011-12-28T20:30:28Z</dc:date>
    </item>
    <item>
      <title>Re: Disable Sources.data</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41589#M9635</link>
      <description>&lt;P&gt;This is possible to disable the global metadata since 4.3.3&lt;BR /&gt;
And in Splunk 5.0 the global metadata are deprecated.&lt;/P&gt;

&lt;P&gt;To disable the Global Metdata and restore full speed indexing :&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;Add option to indexes.conf that disables global metadata generation to handle deployments with rapidly growing sources.data file. (SPL-47689)&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;The side consequence will be that the default summary page will not display values for the "last source/sourcetype/host".&lt;/P&gt;

&lt;P&gt;to apply, edit indexes.conf and add :&lt;BR /&gt;
&lt;CODE&gt;disableGlobalMetadata = true&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;see &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.4/Admin/Indexesconf"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.4/Admin/Indexesconf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Nov 2012 02:02:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Disable-Sources-data/m-p/41589#M9635</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2012-11-13T02:02:07Z</dc:date>
    </item>
  </channel>
</rss>

