Getting Data In

Blacklist inputs.conf is not working..

jay_s
Engager

Greetings!

I am dealing with following directory structure;

var/log/myfolder/log-type_a.log
var/log/myfolder/log-type_b.log
var/log/myfolder/log-type_b1.log
var/log/myfolder/log-type_b2.log
var/log/myfolder/log-type_c.log

I want block log-type_b.log,log-type_b1.log, log-type_b2.log

My inputs.conf

[default]
index = my_default_index
[blacklist:/var/log/myfolder/log-type_b*]

I have tried different variations for blacklist

  • [blacklist:///var/log/myfolder/log-type_b*]

The above blacklist stanza is not working. Please let me know what am I missing.

 

 

 

 

 

Labels (3)
0 Karma
1 Solution

jay_s
Engager

after trying few options
[blacklist:/var/log/myfolder/log-type_b]

seems to be working

View solution in original post

0 Karma

ericjorgensenjr
Path Finder

Try this.

inputs.conf:

[monitor:///var/log/myfolder/]
index = my_default_index
blacklist = log-type_b

 

0 Karma

jay_s
Engager

after trying few options
[blacklist:/var/log/myfolder/log-type_b]

seems to be working

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: Splunk Observability Metrics Cost Optimization

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