Getting Data In

custom Blacklist not working correctly

sushildabare
Path Finder

Trying to make a custom blacklist for one of my input monitor points that excludes certain directories and filetypes


[monitor:///usr/sap/IX4/DVEBMGS26/work]
disabled = false
blacklist = \VM*.$
blacklist = \vm
.$
blacklist = (logs|jtmp)$
blacklist = *.(CPIC|old|trc|dump|DAT|CSV|sql)$
blacklist = \Y_
.*$

[monitor:///sapdb/data/wrk/IX4/knltrace]
disabled = false

[monitor:///sapdb/data/wrk/IX4/dbm.prt]
disabled = false

[monitor:///sapdb/data/wrk/IX4/KnlMsg]
disabled = false


But still files VM*.* and directory logs is not getting blacklisted. Can you please chck if syntax is correct?

Thanks & regards,
Kratika

Tags (1)
0 Karma

jlaw
Splunk Employee
Splunk Employee

In this topic in the docs:

http://docs.splunk.com/Documentation/Splunk/latest/Data/Whitelistorblacklistspecificincomingdata

there's a note: "Important: If you create a blacklist line for each file you want to ignore, Splunk activates only the last filter."

So it sounds like you need to combine your five lines into one in the [monitor:///usr/sap/IX4/DVEBMGS26/work] stanza.

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!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...