<?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: Frozen Time Period in seconds based on Sourcetype in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Frozen-Time-Period-in-seconds-based-on-Sourcetype/m-p/19331#M2730</link>
    <description>&lt;P&gt;Segregate your data in multiple indexes based on the sourcetype. And then specify different retentions per index.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Nov 2012 03:18:03 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2012-11-01T03:18:03Z</dc:date>
    <item>
      <title>Frozen Time Period in seconds based on Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Frozen-Time-Period-in-seconds-based-on-Sourcetype/m-p/19328#M2727</link>
      <description>&lt;P&gt;Why cant I choose a source type of an index instead of the whole index to move my index data from the specific source type chosen to the frozen bucket?&lt;/P&gt;

&lt;P&gt;I dont want to move all of the index, I just want to chose a specific source type within that index to be moved to a cold or frozen bucket at a given specified time.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Nov 2012 01:56:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Frozen-Time-Period-in-seconds-based-on-Sourcetype/m-p/19328#M2727</guid>
      <dc:creator>Dark_Ichigo</dc:creator>
      <dc:date>2012-11-01T01:56:42Z</dc:date>
    </item>
    <item>
      <title>Re: Frozen Time Period in seconds based on Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Frozen-Time-Period-in-seconds-based-on-Sourcetype/m-p/19329#M2728</link>
      <description>&lt;P&gt;The smallest index unit is a bucket.  Sourcetypes are really just a "descriptive marker" on events within a bucket.  You cannot choose different expiry periods for different sourcetypes in a bucket because Splunk's architecture is just not designed that way.&lt;/P&gt;

&lt;P&gt;You can always file an enhancement request asking for this type of functionality.  But, it breaks some pretty foundational tenets of how Splunk indexes work.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Nov 2012 02:47:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Frozen-Time-Period-in-seconds-based-on-Sourcetype/m-p/19329#M2728</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-11-01T02:47:47Z</dc:date>
    </item>
    <item>
      <title>Re: Frozen Time Period in seconds based on Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Frozen-Time-Period-in-seconds-based-on-Sourcetype/m-p/19330#M2729</link>
      <description>&lt;P&gt;What do you reckon would be an alternative then in this case, how can I be able to specify this with Splunks current functionalists..&lt;/P&gt;</description>
      <pubDate>Thu, 01 Nov 2012 03:15:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Frozen-Time-Period-in-seconds-based-on-Sourcetype/m-p/19330#M2729</guid>
      <dc:creator>Dark_Ichigo</dc:creator>
      <dc:date>2012-11-01T03:15:45Z</dc:date>
    </item>
    <item>
      <title>Re: Frozen Time Period in seconds based on Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Frozen-Time-Period-in-seconds-based-on-Sourcetype/m-p/19331#M2730</link>
      <description>&lt;P&gt;Segregate your data in multiple indexes based on the sourcetype. And then specify different retentions per index.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Nov 2012 03:18:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Frozen-Time-Period-in-seconds-based-on-Sourcetype/m-p/19331#M2730</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2012-11-01T03:18:03Z</dc:date>
    </item>
  </channel>
</rss>

