Drop XML event data via transforms.conf

mjemi — Mon, 04 Dec 2023 09:23:26 GMT

I need to drop EventCode 4634 and 4624 with Login_type 3, how i can use nullqueue option and write the correct REGEX on transforms.conf .

Re: Drop XML event data via transforms.conf

_JP — Tue, 05 Dec 2023 00:39:37 GMT

Let's assume your sourcetype is called WindowsEventSourcetype, then you will want to add some lines to that sourcetype's definition in props.conf and transforms.conf:

props.conf

[WindowsEventSourcetype]
TRANSFORMS-t1=eliminate-4624-4634-3

transforms.conf

[eliminate-4624-4634-3]
REGEX=(?m)EventCode\s*=\s*(4624|4634).*?Type\s*=\s*3\s
DEST_KEY=queue
FORMAT=nullQueue

A couple things to note:

These configurations need to be deployed to where your data is "cooked" by Splunk, not searched or the UF. So this means these should be going to Heavy Forwarder(s) and Indexer(s) in your environment that would be ingesting this windows event log data.
I might be slightly off on the regular expression - I can't recall the exact format of the logs. If you could post a couple samples I could tighten this up. Right now the regex is doing something like, "Use multiline mode, look for EventCodes 4624 or 4634, then some more stuff, then Type 3" - I don't recall how the Login_type is labeled within these particular events from Windows.

topic Drop XML event data via transforms.conf in Splunk Search

Drop XML event data via transforms.conf

Re: Drop XML event data via transforms.conf