Getting Data In

Event filtering is not working as expected... what's missing?

cmlombardo
Path Finder

I am pulling my hair off on this one.
I am trying to remove from the windows firewall logs all the IPv6 link local and IPv4 multicast events.
Here are my props and transforms files:

PROPS.CONF

[Windows_Firewall]

TRANSFORMS-7_FilterUselessAddresses = filter_lladdresses, filter_multicast
TRANSFORMS-8_AssignToIndex = windowsfirewall_setindex_default

TRANSFORMS.CONF
[filter_lladdresses]
REGEX = (?i)^(?!.*fe80::).*$
FORMAT = sourcetype::Windows_Firewall
DEST_KEY = MetaData:Sourcetype

[filter_multicast]
REGEX = (?i)^(?!.*224\.0\.0\.).*$
FORMAT = sourcetype::Windows_Firewall
DEST_KEY = MetaData:Sourcetype


[windowsfirewall_setindex_default]
SOURCE_KEY = MetaData:Sourcetype
REGEX = (?i)^sourcetype::Windows_Firewall
DEST_KEY = _MetaData:Index
FORMAT = wf_i

For some reasons which I can't figure out, these events are NOT filtered out.

I need another set of eyes to see what is wrong...

Thank you!

Claudio

Tags (2)
0 Karma
1 Solution

cmlombardo
Path Finder

I solved my problem.

I changed transforms.conf this way:

[filter_lladdresses]
REGEX = (?i)^(?=.*fe80::).*$
DEST_KEY = queue
FORMAT = nullQueue

#Removes multicast traffic (224.0.0) stuff.
[filter_multicast]
REGEX = (?i)^(?=.*224\.0\.0\.).*$
DEST_KEY = queue
FORMAT = nullQueue

Now it works just fine.

View solution in original post

0 Karma

cmlombardo
Path Finder

I solved my problem.

I changed transforms.conf this way:

[filter_lladdresses]
REGEX = (?i)^(?=.*fe80::).*$
DEST_KEY = queue
FORMAT = nullQueue

#Removes multicast traffic (224.0.0) stuff.
[filter_multicast]
REGEX = (?i)^(?=.*224\.0\.0\.).*$
DEST_KEY = queue
FORMAT = nullQueue

Now it works just fine.

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!

How Edge Processor's Durable Queue Works

Edge Processor sits in one of the most consequential places in any Splunk pipeline: between your data sources ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...