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!

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

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...