Getting Data In

Trying to properly format a blacklist for imported files.

mpresseau
New Member

I have configured multiple Data Inputs, pointing at folders such as /mnt/DataInput1 etc. There is a lot of noise so tried following the following links to add a blacklist to the inputs.conf for the input, to restrict junk data such as Level=INFO type linux data.
https://docs.splunk.com/Documentation/Splunk/latest/Data/Whitelistorblacklistspecificincomingdata?r=...

Example input:
[monitor:///mnt/blob/XXXXXXXXXX/logs]
disabled = false
index = customer_XXXX_XXXXXXXX
blacklist = Level="(INFO)"

Unfortunately after several tries, and after making a change, restarting Splunk to see the change, then waiting several hours for the Data Inputs page to queue up the number of files, it still doesn't work.

Can anyone please shed some insight into what I'm doing wrong please?
Ultimately I'd like to do something like:

blacklist = Level="(INFO)"|coderef="(salt*)|"consul)"

Where as you can see above, I want to blacklist =different event types.

Help?

Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

That's not what blacklisting does. The blacklist feature in a monitor statement tells Splunk to ignore any file that matches the given expression. It's often used to skip .gz files, for example.

Filtering certain events within a file is a different feature, which is implemented using transforms. See https://answers.splunk.com/answers/719162/how-do-i-use-propsconf-and-transformsconf-to-filte.html

---
If this reply helps you, Karma would be appreciated.
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 ...