Getting Data In

whitelist blacklist inputs.conf not respected

splunkreal
Influencer

Hello guys,

we used this in inputs.conf according to the Splunk CIM compliant addon for Unix and Linux :


[monitor:///var/log]
whitelist=(messages|secure|auth|maillog|audit\.log|cron)
blacklist=(lastlog|anaconda\.syslog)
disabled = 0
index = linux

However on UF it still looked for /var/log/anaconda/pre-anaconda.log and others, this looks weird behaviour?

Thanks.

Splunk enterprise 7.3.4

UF 7.1.4

 

* If this helps, please upvote or accept solution if it solved *
Labels (1)
0 Karma

harsmarvania57
Ultra Champion

Hi,

 

Your blacklist not correct, if you want to blacklist pre-anaconda.log then use below blacklist.

blacklist=(lastlog|pre-anaconda\.log)
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 ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...