Getting Data In

How to Blacklist on a Universal Forwarder with a TCP input?

pfabrizi
Path Finder

I have a UF running on a linux device, with a TCP input. The input is coming from a Graylog forwarder and all the windows events coming with a 'winlogbeat_ preface.

I want to black list windows events coming by event code and normally I use a blacklist -= EventCode="xxxx" Message=....

however the eventcode comes in as winlogbeat_event_id,
I did try this:
blacklist1= winlogbeat_event_id = "4662"

This doesn't appear to work.

Can someone help with this?

Is there any log that shows events being whitelisted or blacklisted?

Thank You!

0 Karma
1 Solution

FrankVl
Ultra Champion

TCP inputs cannot be filtered with blacklists like that. That only works for WinEventLog inputs.

Perhaps that Graylog forwarder you use can perform some filtering? Otherwise you would have to look at dropping the unwanted events at your Indexers, by routing them to the nullqueue: http://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad#Discard_specific_e...

View solution in original post

0 Karma

FrankVl
Ultra Champion

TCP inputs cannot be filtered with blacklists like that. That only works for WinEventLog inputs.

Perhaps that Graylog forwarder you use can perform some filtering? Otherwise you would have to look at dropping the unwanted events at your Indexers, by routing them to the nullqueue: http://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad#Discard_specific_e...

0 Karma

pfabrizi
Path Finder

Thank You, they can whitelist but not black list or that is what they told us.

Thank You!

0 Karma

FrankVl
Ultra Champion

whitelist = foo also doesn't work on a UF TCP input.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...