Getting Data In

How and where do I configure props and transforms to forward a few events into a particular index by host?

allan_newton
Path Finder

Hi,

I have 4 forwarders, 4 search heads, and 2 forwarders in my Splunk cluster. Now one of the forwarders is configured to read data from UDP port 514. The data comes in to the forwarder and it then is forwarded to the indexers.

Now I need to apply configurations in transforms.conf and props.conf to write few events into a separate index by host. Where do I put those configurations? Should I do the changes in the forwarder or the indexer?

Thanks.

0 Karma
1 Solution

MuS
Legend

Hi allan_newton,

try something like this,un-tested and out of my head:

props.conf

[source::udp:514]
TRANSFORMS-001_changemetadata = redirect_to_index_foo

transforms.conf

[redirect_to_index_foo]
SOURCE_KEY = MetaData:Host
REGEX = ^host::(10.10.10.d+)$
FORMAT = foo
DEST_KEY = _MetaData:Index

Don't forget to restart the forwarder after you changed the props and transforms.
Hope this helps ...

cheers, MuS

View solution in original post

0 Karma

MuS
Legend

Hi allan_newton,

try something like this,un-tested and out of my head:

props.conf

[source::udp:514]
TRANSFORMS-001_changemetadata = redirect_to_index_foo

transforms.conf

[redirect_to_index_foo]
SOURCE_KEY = MetaData:Host
REGEX = ^host::(10.10.10.d+)$
FORMAT = foo
DEST_KEY = _MetaData:Index

Don't forget to restart the forwarder after you changed the props and transforms.
Hope this helps ...

cheers, MuS

0 Karma

allan_newton
Path Finder

Instead of ^host::(10.10.10.d+)$ can i use host::(10.10.10.32) ?

0 Karma
Get Updates on the Splunk Community!

Aligning Observability Costs with Business Value: Practical Strategies

 Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...