Getting Data In

Change host props and transforms not working

wvalente
Explorer

Guys,

I need a help.

I've configured the props and transforms to change the host field from a lambda function I'm collecting the logs.

I can see the new host, but I not find anything when I search the new host with host=....

I done this configuration in heavy forwarder. This heavy forwarder concentrate the logs and sends it to a splunk cluster with two indexers and auto load balancing configuration.

The host that I'm trying to change is coming from a lambda function from guradduty.

props.conf

[aws:cloudwatch:guardduty]
TRANSFORMS-client = rename_host_guardduty
SHOULD_LINEMERGE = false

transforms.conf

[rename_host_guardduty]
DEST_KEY = MetaData:Host
REGEX = .*
FORMAT = guardduty

Any ideas?

Thank you.

Labels (3)
0 Karma
1 Solution

willemjongeneel
Communicator

Hello,

I think you should change format to: 

FORMAT = host::guardduty

Kind regards,

Willem

View solution in original post

0 Karma

willemjongeneel
Communicator

Hello,

I think you should change format to: 

FORMAT = host::guardduty

Kind regards,

Willem

0 Karma

wvalente
Explorer

Hi Willem.

I've done here and it's work very well.

Thank you so much.

Tags (1)
0 Karma

wvalente
Explorer

Hi Willem,

I'll try here.

Thank you.

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!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...