Getting Data In

Copying over data to another index for longer retention

jpillai
Path Finder

Hi all,

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?

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.

We want to retain the original source/sourcetype etc and have the subset of topics that we need longer retention be copied over to another index, say index2, that has longer retention.

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.

 

 

Labels (3)
0 Karma

P_vandereerden
Splunk Employee
Splunk Employee

I believe that your scenario could be accomplished with Ingest Actions:
https://docs.splunk.com/Documentation/Splunk/9.2.1/Data/DataIngest

This should support cloning data and applying different filtering rules and routing to the two streams.

Paul van der Eerden,
Breaking software for over 20 years.
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Maximizing the Value of Splunk ES 8.x

Splunk Enterprise Security (ES) continues to be a leader in the Gartner Magic Quadrant, reflecting its pivotal ...