Getting Data In

What is the best way to fork events into a new sourcetype that will eventually become the only sourcetype?

thisissplunk
Builder

Basically, I want to have ONE log file populating TWO sourcetypes at the same time. Identical events in both. Eventually, I'll kill off the old sourcetype and only have the events going into the sourcetype with the new name.

I'm doing this because I want to check parity and catch bugs or other issues for the new sourcetype. What is the best approach for this?

0 Karma

esix_splunk
Splunk Employee
Splunk Employee

So to clarify, you are indexing one log file, twice, as two different sourcetypes.

If you are indexing the same file twice, what kind of differences are you expecting to catch?

In the end, you just drop the monitor / input for the sourcetype you want to get rid of.

0 Karma
Get Updates on the Splunk Community!

Update Your SOAR Apps for Python 3.13: What Community Developers Need to Know

To Community SOAR App Developers - we're reaching out with an important update regarding Python 3.9's ...

October Community Champions: A Shoutout to Our Contributors!

As October comes to a close, we want to take a moment to celebrate the people who make the Splunk Community ...

Automatic Discovery Part 2: Setup and Best Practices

In Part 1 of this series, we covered what Automatic Discovery is and why it’s critical for observability at ...