Getting Data In

How do I route data based on the Index field

mzorzi
Splunk Employee
Splunk Employee

Assuming I have a forwarder with inputs.conf:

[monitor:///var/log/notcritical]
index=datacritical

[monitor:///var/log/critical]
index=datanoncritical

How can I route the events from the two files into two different Splunk Indexers based purely on the value of Indexer field?

0 Karma
1 Solution

mzorzi
Splunk Employee
Splunk Employee

You should be able to forward based on value in the index field with this transforms.conf.

[send_to_critical]
SOURCE_KEY = _MetaData:Index
REGEX = datacritical
DEST_KEY = _TCP_ROUTING
FORMAT = critical

[send_to_noncritical]
SOURCE_KEY = _MetaData:Index
REGEX = datanoncritical
DEST_KEY = _TCP_ROUTING
FORMAT = noncritical

You the need to create a props.conf and make sure these two rules are applied to each event. You will then also need an outputs.conf with the two different tcpout groups, critical and noncritical.

View solution in original post

mzorzi
Splunk Employee
Splunk Employee

You should be able to forward based on value in the index field with this transforms.conf.

[send_to_critical]
SOURCE_KEY = _MetaData:Index
REGEX = datacritical
DEST_KEY = _TCP_ROUTING
FORMAT = critical

[send_to_noncritical]
SOURCE_KEY = _MetaData:Index
REGEX = datanoncritical
DEST_KEY = _TCP_ROUTING
FORMAT = noncritical

You the need to create a props.conf and make sure these two rules are applied to each event. You will then also need an outputs.conf with the two different tcpout groups, critical and noncritical.

Get Updates on the Splunk Community!

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 ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...