Getting Data In

How to split event to two indexes?

klim
Path Finder

I would like to know if it is possible to be able to inject an event to a heavy forwarder via the hec and then have it be split into two events and sent to different indexes.

For example I have the original log line of:

ID=1 time=”2022-12-29 16:57:41 UTC” name=”person” address=”abc” message=”some note”.

I want the event to be split but the two new events can share similar fields.

So index1 would be:  

ID=1 time=”2022-12-29 16:57:41 UTC” name=”person” address=”abc”

And index2 would be:

ID=1 time=”2022-12-29 16:57:41 UTC” message=”some note”

Labels (3)
Tags (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

I believe it can be done.  Use the CLONE_SOURCETYPE setting in transforms.conf to create a copy of the event and give it a new sourcetype.   Then each sourcetype should be able to use REGEX and FORMAT settings to select the fields they want.

You'd think that the new Ingest Actions feature would be perfect for this, but it does not offer the type of changes you want to make.

This would be easier using Cribl (http://cribl.io).

Either way, duplicating the events means doubling your ingest, with corresponding effects on your license and storage.

---
If this reply helps you, Karma would be appreciated.
0 Karma

klim
Path Finder

thanks. doubling my ingest doesn't sound like a great idea. It would be cheaper to send two requests.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...