Getting Data In

How do I edit my Hosts > Heavy Forwarder > Heavy Forwarder > Indexers configuration to route data to different target groups based on metadata?

rgomatha
Explorer

I have gone through the docs: routing based on meta data (source, host, sourcetype) to send specific data to a different target group, but isn't working.

I have 10 hosts that send data to an intermediate Heavy Forwarder (HF1), and that sends to another intermediate Heavy Forwarder (HF2) and finally to the indexers.

On the second intermediate forwarder, I added
Props.conf

[host::(host1|host2|.....|host10)]
TRANSFORMS_routing = missioncritical_hosts

On transforms.conf

[missioncritical_hosts]
REGEX=.
DEST_KEY=_TCP_ROUTING
FORMAT=target_group2

On outputs.conf

[tcpout]
default-group = target_group1

[tcpout:target_group2]
server = idxr2:9997

Restarted splunkd, no errors in splunkd.log

No data from that HF related to missioncritical_servers on the original index mshosts or main. What am I missing?

Thanks in advance!
Avanthi

renjith_nair
Legend

Can you try with one host in the props and see if it's working?

As per doc the host field should be

 host::<host>, where <host> is the host, or host-matching pattern, for an event.

So either it should be a host or a host pattern like myhost* for myhost1,myhost2, etc

If it's working for one host, then you can confirm it's the problem with props.

Happy Splunking!
0 Karma
Get Updates on the Splunk Community!

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...