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.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...