Getting Data In

How do I edit my inputs.conf to blacklist Windows event logs with Eventcode 7036 on my Splunk 6.1.3 universal forwarder?

chrisbaker
New Member

Hi,

I'm trying to use blacklist on the Universal Forwarder to prevent unwanted events from being sent and indexed. Splunk instance and UF are both version 6.1.3
On the machine with UF, I went to C:\Program Files\SplunkUniversalForwarder\etc\system\local
The inputs.conf file looks like this:

 [default]
 host = Win7HP8440p

 [script://$SPLUNK_HOME\bin\scripts\splunk-wmi.path]

So I added a stanza as shown in many models and now it looks like this:

 [default]
 host = Win7HP8440p

 [WinEventLog://System]
 disabled = false
 blacklist1 = 7036

 [script://$SPLUNK_HOME\bin\scripts\splunk-wmi.path]

I rebooted the host with the UF and then checked on the Splunk instance and Event code 7036 keeps coming through.
I have tried many variations to match the examples I have seen ( like disabled = 0 or removing spaces around = signs etc.) but so far nothing seems to work.

Any suggestions?

0 Karma

juvetm
Communicator

hi
are you using the advanced filtering format

0 Karma

chrisbaker
New Member

How do I check for that? I don't see anything in the docs.

0 Karma

satishsdange
Builder

Any reason to add 1 to blacklist? It could be simply "blacklist = 7036"

0 Karma

chrisbaker
New Member

I've tried with and without the 1. I saw it as "blacklist1" in some examples.

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!

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

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...