Getting Data In

What are the sequence of execution transforms across different stanza and locations?

fxyfrank_acn
Explorer

Hi,

We want to change sourcetype and then send data to two different Splunk Indexers.

What is happening is the sourcetype is getting changed (that means first props.conf stanza is working) BUT the seconds props.conf stanza present in the apps folder is not working (It is only sending the logs to default output group).

Configuration files for change sourcetypes are located in the /system/local folder and route data configuration files are in the /apps/application/local/ folder.

Does anyone have similar issue? Thanks!

SPLUNK_HOME/etc/system/local/

props.conf

[source::/abc/xyz.log]
TRANSFORMS-changesourcetype = st

transforms.conf

[st]
REGEX = \.*\[12345]\.*
FORMAT = sourcetype::sourcetype1
DEST_KEY = MetaData:Sourcetype

SPLUNK_HOME/etc/apps/application/local

props.conf

[sourcetype1]
TRANSFORMS-routing = route_data

transforms.conf

[route_data]
REGEX = .
DEST_KEY = _TCP_ROUTING
FORMAT = indexer1, indexer2
0 Karma
1 Solution

chrisyounger
SplunkTrust
SplunkTrust

The sourcetype is only checked once as the event enters the pipeline. So change your routing to be for [source::/abc/xyz.log] instead

View solution in original post

0 Karma

chrisyounger
SplunkTrust
SplunkTrust

The sourcetype is only checked once as the event enters the pipeline. So change your routing to be for [source::/abc/xyz.log] instead

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!

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