Getting Data In

Include Windows Event Log and Exclude LognType

ajith_sukumaran
Explorer

Hi, I have a requirement for forward 4 Windows Log EventCodes 4672, 4673, 4674 & 4624 to a destination from the HWFs, however exclude if these EventCode messages are for the "Logon Type=3" and forward rest everything.

Expected result is something like:

EventCode=4672 & LogonType= 3 : DISCARDED
EventCode=4673 & LogonType= 3 : DISCARDED
EventCode=4675 & LogonType= * : DISCARDED

EventCode=4672 & LogonType= 2 : PROCESSED

etc

Does the below settings in the props and conf really help for this ? Thanks in advance.

cat outputs.conf

[syslog:syslog_destination]
server=:514
type=udp
disabled=false

cat props.conf

[WinEventLog:Security]
TRANSFORMS-routing = routeDestination,excludeDestination

cat transforms.conf

[routeDestination]
REGEX=EventCode=(4672|4673|4674|4624)
DEST_KEY=_SYSLOG_ROUTING
FORMAT=syslog_destination

[excludeDestination]
REGEX=Logon\sType:\t+3
DEST_KEY = queue
FORMAT = nullQueue
0 Karma

3no
Communicator

For the eventCode filtering you can simply use Whitelist in inputs.conf to only collect EventCode 4672, 4673, 4674 & 4624.

https://docs.splunk.com/Documentation/Splunk/8.0.2/Admin/Inputsconf (see whitelist for Windows Event Log Monitor)

And after, only have the excludeDestination as a stanza in your transforms.conf.


Otherwise I think you configuration is okay, but you'll have to change your props.conf to :

 [WinEventLog:Security]
 TRANSFORMS-routing = excludeDestination, routeDestination

Because you want first to discard the Logon_Type=3 then keep the log if the EventCode match, not the other way around because the EventCode will always match and therefore it will always use the routeDestination.

It works like ACL, first matched, first served.

3no

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...