Getting Data In

How to specify an index for storing data from forwarders

nickcode
Explorer

How to specify different indexes for storing data of different source(sourcetype)? The data is coming from remote forwarders.

0 Karma
1 Solution

Ayn
Legend

Define an index-time transform on the indexer and have it apply to the appropriate events.

For example:

props.conf:

[myfavoritesourcetype]
TRANSFORMS-index=sendtomyindex

transforms.conf:

[sendtomyindex]
REGEX=.
DEST_KEY=_MetaData:Index
FORMAT=myindex
WRITE_META=true

View solution in original post

Ayn
Legend

Define an index-time transform on the indexer and have it apply to the appropriate events.

For example:

props.conf:

[myfavoritesourcetype]
TRANSFORMS-index=sendtomyindex

transforms.conf:

[sendtomyindex]
REGEX=.
DEST_KEY=_MetaData:Index
FORMAT=myindex
WRITE_META=true

Ayn
Legend

See martin's answer for more info on that.

0 Karma

nickcode
Explorer

Thank you, I'll try it. By the way, how to get it right from the start on the forwarders as you refered above.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

nickcode
Explorer

martin_mueller's solution may not be suitable for my requirement. Then, how to use transforms on the indexer or config the forwarders, Ayn?

0 Karma

Ayn
Legend

...on the remote forwarders that is.

If you can't affect how things are setup on these forwarders, you can also rewrite which index events are stored in by using transforms on the indexer. But really, the best thing is to get it right from the start on the forwarders instead.

Get Updates on the Splunk Community!

New Case Study Shows the Value of Partnering with Splunk Academic Alliance

The University of Nevada, Las Vegas (UNLV) is another premier research institution helping to shape the next ...

How to Monitor Google Kubernetes Engine (GKE)

We’ve looked at how to integrate Kubernetes environments with Splunk Observability Cloud, but what about ...

Index This | How can you make 45 using only 4?

October 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...