Splunk Enterprise

Data forwarding to third party from HWF and stopping ingestion to Indexer

rtantra
New Member

Hi All,

Currently we are using Opsec add on to get data into SPlunk  and forwarding the duplicate copy of same data to third party (logstash).Now we want to use existing opsec add on to pull the data and forward it to third party only and stop forwarding to SPlunk indexer. Below is log flow

Data Flow:

Opsec Manger >> Splunk HWF(opsec add on) >>Forward to Indexer

                                                                                              >> forward to third party (logstash)

Questions:

Is it possible to pull data and forward only to third party without ingesting to Splunk? if yes how?

 

Below sis our existing config:

Config for data forwarding to third party:

 

props on hwf 

[opsec]

TRANSFORMS-routing=routelogstash

Transforms.conf on HWF

[routelogstash]

REGEX= .

DEST_KEY = SYSLOG_ROUTING

FORMAT=syslog_tcp_test

 outputs.conf on HWF

[syslog:syslog_tcp_test]

server=thirdparty serevrname:port

 

We have seprate outputs.conf for data forking to Indexers.We tried setnull and setparsing to stop data ingestion to splunk but no luck.Please suggest

 

0 Karma

rtantra
New Member

@scelikok ,

Tried suggested config but no luck. Its stopping log ingestion and log forwarding both 😞

0 Karma

scelikok
Champion

Hi @rtantra,

Can you try sending to nullqueue before sending to syslog?

props on hwf 

[opsec]
TRANSFORMS-routing=setnull,routelogstash

Transforms.conf on HWF

[routelogstash]
REGEX= .
DEST_KEY = SYSLOG_ROUTING
FORMAT=syslog_tcp_test

[setnull]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue


outputs.conf on HWF

[syslog:syslog_tcp_test]
server=thirdparty servername:port
If this reply helps you an upvote is appreciated.
0 Karma
Register for .conf21 Now! Go Vegas or Go Virtual!

How will you .conf21? You decide! Go in-person in Las Vegas, 10/18-10/21, or go online with .conf21 Virtual, 10/19-10/20.