<?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: Copying over data to another index for longer retention in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Copying-over-data-to-another-index-for-longer-retention/m-p/691126#M114967</link>
    <description>&lt;P&gt;I believe that your scenario could be accomplished with Ingest Actions:&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.2.1/Data/DataIngest" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.2.1/Data/DataIngest&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;This should support cloning data and applying different filtering rules and routing to the two streams.&lt;/P&gt;</description>
    <pubDate>Wed, 19 Jun 2024 17:32:59 GMT</pubDate>
    <dc:creator>P_vandereerden</dc:creator>
    <dc:date>2024-06-19T17:32:59Z</dc:date>
    <item>
      <title>Copying over data to another index for longer retention</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Copying-over-data-to-another-index-for-longer-retention/m-p/691101#M114962</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We are indexing different topics from our kafka cluster to an index say, index1. But we now have a requirement to retain a subset of those topics for longer period of time. Is there a way to implement this while we still get all the data into the same index?&lt;/P&gt;&lt;P&gt;I can think of the subset of topics that I need longer retention being searched, filtered out and collected to a new index. But this involves licensing if we want to retain the source/sourcetype and other fields I believe which is not practical for us.&lt;/P&gt;&lt;P&gt;We want to retain the original source/sourcetype etc and have the&amp;nbsp;subset of topics that we need longer retention be copied over to another index, say index2, that has longer retention.&lt;/P&gt;&lt;P&gt;We also need the original copy in index1 as we have lot of dependant searches and alerts that use this index to search for the same data.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jun 2024 13:53:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Copying-over-data-to-another-index-for-longer-retention/m-p/691101#M114962</guid>
      <dc:creator>jpillai</dc:creator>
      <dc:date>2024-06-19T13:53:02Z</dc:date>
    </item>
    <item>
      <title>Re: Copying over data to another index for longer retention</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Copying-over-data-to-another-index-for-longer-retention/m-p/691126#M114967</link>
      <description>&lt;P&gt;I believe that your scenario could be accomplished with Ingest Actions:&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.2.1/Data/DataIngest" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.2.1/Data/DataIngest&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;This should support cloning data and applying different filtering rules and routing to the two streams.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jun 2024 17:32:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Copying-over-data-to-another-index-for-longer-retention/m-p/691126#M114967</guid>
      <dc:creator>P_vandereerden</dc:creator>
      <dc:date>2024-06-19T17:32:59Z</dc:date>
    </item>
  </channel>
</rss>

