<?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: Does frozenTimePeriodInSecs work in [default]? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Does-frozenTimePeriodInSecs-work-in-default/m-p/335219#M163333</link>
    <description>&lt;P&gt;The information you see under [default] is a global setting that take precedence if you haven't defined a setting for a specific index. These settings come from &lt;CODE&gt;/etc/system/default/indexes.conf&lt;/CODE&gt;. This can be a bit confusing as if you look into indexes.conf, global settings do not exist within a [default] stanza. Additionally, there is no need to create a [default] stanza.&lt;/P&gt;

&lt;P&gt;If you take a look at the settings in &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/indexes.conf&lt;/CODE&gt;, you'll notice the settings for &lt;CODE&gt;frozenTimePeriodInSecs&lt;/CODE&gt; matches the setting under this section:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;code&amp;gt;# index specific defaults
frozenTimePeriodInSecs = 188697600
&amp;lt;/code&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Since this setting also exists for [main], per the btool ouput, the setting for main takes precedence. This is part of the reason that btool is a technical support utility. The output can be confusing if you aren't sure what to expect. In this instance, since btool does show main as having the value defined, you can be sure that this is what will take effect. If you wanted to ensure all indexes had this behavior by default, you could copy the global settings from &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/indexes.conf&lt;/CODE&gt; into &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/indexes.conf&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;Also,&lt;BR /&gt;
You set it in &lt;CODE&gt;local/indexes.conf&lt;/CODE&gt; on an &lt;CODE&gt;index per index basis&lt;/CODE&gt;. &lt;BR /&gt;
And yes you can do it exactly as you state.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Setaretirementandarchivingpolicy"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Setaretirementandarchivingpolicy&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[your_custom_index]
 frozenTimePeriodInSecs = &amp;lt;retention_period&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;let me know if this helps!&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jan 2018 05:56:36 GMT</pubDate>
    <dc:creator>mayurr98</dc:creator>
    <dc:date>2018-01-26T05:56:36Z</dc:date>
    <item>
      <title>Does frozenTimePeriodInSecs work in [default]?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Does-frozenTimePeriodInSecs-work-in-default/m-p/335217#M163331</link>
      <description>&lt;P&gt;I have a local indexes.conf file on all my indexers:&lt;BR /&gt;
    [default]&lt;BR /&gt;
&lt;CODE&gt;frozenTimePeriodInSecs = 63072000&lt;/CODE&gt;           # 2 yr&lt;BR /&gt;
    [main]&lt;BR /&gt;
&lt;CODE&gt;frozenTimePeriodInSecs = 15552000&lt;/CODE&gt;           # 180d&lt;/P&gt;

&lt;P&gt;This seems to have worked on main but not on any other indexes. Does frozenTimePeriodInSecs work in [default]? Or do I have to enter a value for each index? Or should I put the value outside a stanza?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 20:53:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Does-frozenTimePeriodInSecs-work-in-default/m-p/335217#M163331</guid>
      <dc:creator>wsanderstii</dc:creator>
      <dc:date>2018-01-25T20:53:41Z</dc:date>
    </item>
    <item>
      <title>Re: Does frozenTimePeriodInSecs work in [default]?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Does-frozenTimePeriodInSecs-work-in-default/m-p/335218#M163332</link>
      <description>&lt;P&gt;The attribute &lt;CODE&gt;frozenTimePeriodInSecs&lt;/CODE&gt; is per index option, so it should be specified in the stanza for each index. Without specifying it, default value of it would be 6 years or 188697600. &lt;/P&gt;

&lt;P&gt;When you specify it in &lt;CODE&gt;[default]&lt;/CODE&gt; section, it's getting applied to default index which is main (as specified in attribute &lt;CODE&gt;defaultDatabase&lt;/CODE&gt;)&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 21:00:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Does-frozenTimePeriodInSecs-work-in-default/m-p/335218#M163332</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2018-01-25T21:00:29Z</dc:date>
    </item>
    <item>
      <title>Re: Does frozenTimePeriodInSecs work in [default]?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Does-frozenTimePeriodInSecs-work-in-default/m-p/335219#M163333</link>
      <description>&lt;P&gt;The information you see under [default] is a global setting that take precedence if you haven't defined a setting for a specific index. These settings come from &lt;CODE&gt;/etc/system/default/indexes.conf&lt;/CODE&gt;. This can be a bit confusing as if you look into indexes.conf, global settings do not exist within a [default] stanza. Additionally, there is no need to create a [default] stanza.&lt;/P&gt;

&lt;P&gt;If you take a look at the settings in &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/indexes.conf&lt;/CODE&gt;, you'll notice the settings for &lt;CODE&gt;frozenTimePeriodInSecs&lt;/CODE&gt; matches the setting under this section:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;code&amp;gt;# index specific defaults
frozenTimePeriodInSecs = 188697600
&amp;lt;/code&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Since this setting also exists for [main], per the btool ouput, the setting for main takes precedence. This is part of the reason that btool is a technical support utility. The output can be confusing if you aren't sure what to expect. In this instance, since btool does show main as having the value defined, you can be sure that this is what will take effect. If you wanted to ensure all indexes had this behavior by default, you could copy the global settings from &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/indexes.conf&lt;/CODE&gt; into &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/indexes.conf&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;Also,&lt;BR /&gt;
You set it in &lt;CODE&gt;local/indexes.conf&lt;/CODE&gt; on an &lt;CODE&gt;index per index basis&lt;/CODE&gt;. &lt;BR /&gt;
And yes you can do it exactly as you state.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Setaretirementandarchivingpolicy"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Setaretirementandarchivingpolicy&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[your_custom_index]
 frozenTimePeriodInSecs = &amp;lt;retention_period&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;let me know if this helps!&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jan 2018 05:56:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Does-frozenTimePeriodInSecs-work-in-default/m-p/335219#M163333</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-01-26T05:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: Does frozenTimePeriodInSecs work in [default]?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Does-frozenTimePeriodInSecs-work-in-default/m-p/335220#M163334</link>
      <description>&lt;P&gt;Actually what worked was putting "frozenTimePeriodInSecs = 63072000" (2 years) &lt;STRONG&gt;outside of any stanza&lt;/STRONG&gt; in /opt/splunk/etc/master-apps/_cluster/local/indexes.conf.&lt;/P&gt;

&lt;P&gt;Thanks for the replies.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jan 2018 17:29:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Does-frozenTimePeriodInSecs-work-in-default/m-p/335220#M163334</guid>
      <dc:creator>wsanderstii</dc:creator>
      <dc:date>2018-01-26T17:29:14Z</dc:date>
    </item>
  </channel>
</rss>

