Getting Data In

How to route data with props and transforms over multiple HF?

CMEOGNAD
Engager

Hi Community,

how to route data with props and transforms over multiple HF?

Source A to Data Collector > IDX Cluster A
|
(Data Copy A)
|
|---> Source B to Data Collector > IDX Cluster A/B

Currently, the routing only works directly to IDX Cluster A/B, but not via Source B HF

Please Help - Markus

0 Karma

PickleRick
SplunkTrust
SplunkTrust

If you want to have your data processed by HFA then sent to HFB where it will again be processed by props/transforms and then sent to indexers... That can't be done unless you do something ugly in between like sending HFA->HFB via syslog or HEC. Your data stream is parsed at the first parsing Splunk instance in event's path. Then it's passed as parsed data and not touched any more.

0 Karma

CMEOGNAD
Engager

"Source A" to Data Collector 01  > IDX Cluster 01 for Data A
|
(Data Copy from Source A for Cluster 02)
|
|---> "Source B" to Data Collector 02 > IDX Cluster 02 for Data A and B

THX for the link, my config is similar, but... the "Data A" Copy from DC01 direct to IDX Cluster 02 works fine, "Data A" Copy from DC01 to DC02 to IDX Cluster 02 not...

Any idea?
Is "Data HF hopping" 😉 even possible?
Without transforms and props directly via tcp-out over inputs.conf it worked...

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @CMEOGNAD,

if DataA is a different Universal Forwarder, you could directly send data to both the DCs not passing throgh DC1.

You can configure in outputs.conf (as described in the documentation) a "fork" to send data to both the destinations.

Ciao.

Giuseppe

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @CMEOGNAD,

lete me understand: are Source A and SourceB different systems with Universal Forwarders or different Data Source on the same Universal Forwarder, or what else?

If they are different Universal Forwarders you can use a different outputs.con on each one.

If they are different Data Sources on the same Universal Forwarder, you have to follow the instructions at https://docs.splunk.com/Documentation/Splunk/9.0.3/Forwarding/Routeandfilterdatad#Route_inputs_to_sp... 

Ciao.

Giuseppe

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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...