Splunk Enterprise

Tagging Heavy Forwarders

jotne
Builder

This is a tip, not a question😃

When you have a large solution, you can see on the log data: what the UF name that data comes from, what Index server data are stored on.  What you do not see are what Heavy Forwarders data are passing trough.  Here is an app that do just that.  Adding an extra field does not use extra license, since only _raw length are calculated.

Make an app that you sends to all HF servere:

app name: set_name_gateway_hf

props.conf (will apply to all data)

 

 

[source::...]
TRANSFORMS_set_hf_server_name = set_hf_server_name

 

 

transforms.conf

 

 

[set_hf_server_name]
INGEST_EVAL = splunk_hf_name := splunk_server

 

 

This will use the Splunk HF server name from etc/system/local/server.conf

Labels (2)
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 ...