Quantcast
Channel: Questions in topic: "heavy-forwarder"
Viewing all articles
Browse latest Browse all 727

Using Heavy Forwarded to Send Subset of Data to 3rd Party and Not Index

$
0
0
Having issues with routing data to a 3rd party and then dropping the events from being indexed. The Windows event is being sent to the 3rd party but also is being indexed. I currently have a case open with support but wanted to ask the question to see if anyone has dealt with the issue before. -bash-4.2$ more props.conf [source::WinEventLog:Security] TRANSFORMS-pta = pta_syslog_filter [WinEventLog:Security] TRANSFORMS-eventcodes = badevents -bash-4.2$ more transforms.conf #Send eventcode 4624 to 3rd party [pta_syslog_filter] REGEX = .*EventCode=4624.* DEST_KEY =_SYSLOG_ROUTING FORMAT = pta_syslog Windows events to drop. If I add 4624 below, the events are not sent to 3rd party. [badevents] REGEX=(?m)EventCode=(4634|560|562|5156|4689|4648|4662|4769|5061|5058) DEST_KEY=queue FORMAT=nullQueue -bash-4.2$ more outputs.conf [tcpout] defaultGroup = default-autolb-group [syslog:pta_syslog] server = 3rdPartyHostIP:11514 sendCookedData = false type=udp timestampformat = %s Splunk indexers [tcpout:default-autolb-group] server = indexer1:9997, indexer2:9997 autoLB = true

Viewing all articles
Browse latest Browse all 727

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>