Getting Data In

How to forward only specific Windows eventlogs via Splunk Universal forwarder

chimbudp
Contributor

I need to monitor only logs with Event code = 5410,6913.
How can i setup this in forwarder ?
please suggest some help

Tags (2)
1 Solution

lukejadamec
Super Champion

This is what the book says to do...

On the forwarder, you need to enable the WinEventLog:Security input.

On the indexer you need to create entries in your system/local/props.conf and system/local/transforms.conf

props.conf

[source::*:Security]

TRANSFORMS-set=setnull,setparsing

transforms.conf

[setnull]

REGEX = .

DEST_KEY = queue

FORMAT = nullQueue

[setparsing]

REGEX =(?m)^EventCode=(5410|6913)

DEST_KEY = queue

FORMAT = indexQueue

View solution in original post

sbrant_splunk
Splunk Employee
Splunk Employee

As of Splunk 6, there is a simpler way to filter which Windows events are forwarded by Splunk.

See whitelist and blacklist in the "Windows Event Log Monitor" section of the following doc: http://docs.splunk.com/Documentation/Splunk/latest/admin/Inputsconf

lukejadamec
Super Champion

This is what the book says to do...

On the forwarder, you need to enable the WinEventLog:Security input.

On the indexer you need to create entries in your system/local/props.conf and system/local/transforms.conf

props.conf

[source::*:Security]

TRANSFORMS-set=setnull,setparsing

transforms.conf

[setnull]

REGEX = .

DEST_KEY = queue

FORMAT = nullQueue

[setparsing]

REGEX =(?m)^EventCode=(5410|6913)

DEST_KEY = queue

FORMAT = indexQueue

Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...