Getting Data In

Windows Event Log Filter Attempt Failing

jchensor
Communicator

Hello, everyone.

I've looked at the following pages in Splunk Answers already, but after following everything they've done in there, I still cannot get my situation to work. 😞 But I looked through these:

http://splunk-base.splunk.com/answers/577/how-do-you-filter-windows-event-log
http://splunk-base.splunk.com/answers/13093/remote-event-log-windows-filtering-by-eventcode-not-work...
http://splunk-base.splunk.com/answers/29218/filtering-windows-event-logs

So I basically have the same problem as the first link, but I can't get it to work, even with the techniques used in that issue. I want to filter out certain Windows Events by EventCode, but the settings don't seem to take. Here's my settings:

-- PROPS.CONF --

[WinEventLog:Security]
TRANSFORMS-wineventlog-security = wineventlog_security_setNull

-- TRANSFORMS.CONF --

[wineventlog_security_setNull]
REGEX = (?msi)^EventCode=4674\D
DEST_KEY = queue
FORMAT = nullQueue

I'm putting this on the Forwarder machine, as this occurs on the Forwarders, correct? Or should this be on the Indexers?

Thanks everyone!

  • James
0 Karma
1 Solution

MuS
SplunkTrust
SplunkTrust

Hi jchensor

props.conf and transforms.conf are only handled on heavy forwarder and not on light or universal forwarder.

If your forwarder is s heavy, you could put props.conf and transforms.conf there.

If your forwarder is a light or universal forwarder, you must put your props.conf and transforms.conf on the indexer.

hope this helps

cheers,
MuS

View solution in original post

yannK
Splunk Employee
Splunk Employee
0 Karma

MuS
SplunkTrust
SplunkTrust

Hi jchensor

props.conf and transforms.conf are only handled on heavy forwarder and not on light or universal forwarder.

If your forwarder is s heavy, you could put props.conf and transforms.conf there.

If your forwarder is a light or universal forwarder, you must put your props.conf and transforms.conf on the indexer.

hope this helps

cheers,
MuS

jchensor
Communicator

Ahhhh, yes. ^_^ Thanks. Moving it to the indexer made it work exactly as I wanted. Thanks so much!!

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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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 ...