Getting Data In

How do you filter windows logs by level?

crsupportddc
Explorer

Is there any way to get only critical and error logs from Windows?

I mean, Windows generates logs using different levels (Critical, Warning, Error, Information...) and I don't want the Information logs on Splunk, so I would like to configure the forwarder to not send them.

0 Karma
1 Solution

whrg
Motivator

Hello @crsupportddc,

So I assume the Windows events (which are multiline) contain this line which you want to base your filter on:

Type=Information

Check out this page on how to filter specific events: Discard specific events and keep the rest.

On your heavy forwarder/indexer (whatever system comes after the Universal Forwarder), add the following lines to props.conf:

[WinEventLog:Application]
TRANSFORMS-filter = filter_information
[WinEventLog:Security]
TRANSFORMS-filter = filter_information
[WinEventLog:System]
TRANSFORMS-filter = filter_information

WinEventLog:Application, WinEventLog:Security and WinEventLog:System refer to the sourcetypes.

And add the following lines to transforms.conf:

[filter_information]
REGEX = Type=Information
DEST_KEY = queue
FORMAT = nullQueue

Do not forget to restart Splunk after making these changes.

View solution in original post

whrg
Motivator

Hello @crsupportddc,

So I assume the Windows events (which are multiline) contain this line which you want to base your filter on:

Type=Information

Check out this page on how to filter specific events: Discard specific events and keep the rest.

On your heavy forwarder/indexer (whatever system comes after the Universal Forwarder), add the following lines to props.conf:

[WinEventLog:Application]
TRANSFORMS-filter = filter_information
[WinEventLog:Security]
TRANSFORMS-filter = filter_information
[WinEventLog:System]
TRANSFORMS-filter = filter_information

WinEventLog:Application, WinEventLog:Security and WinEventLog:System refer to the sourcetypes.

And add the following lines to transforms.conf:

[filter_information]
REGEX = Type=Information
DEST_KEY = queue
FORMAT = nullQueue

Do not forget to restart Splunk after making these changes.

crsupportddc
Explorer

Thank you for the help.
I managed to create a blacklist and avoid some specific logs but I'll implement what you mentioned to completely ignore the Information logs.

whrg
Motivator

Filtering by blacklisting specific EventCodes works as well. Good thinking.

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!

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...