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.

---
What goes around comes around. If it helps, hit it with Karma 🙂
0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...