Security

ERROR TailingProcessor - matching incorrect files?

lakshman237
Path Finder

I have my inputs.conf as follows on a linux env.

[monitor:///mydomain/logs/project/mytestlogs*.txt]
blacklist = .(gz)$
whitelist = mytestlogs[1-4]{1}.txt
disabled = false
followTail = 0
recursive = false
sourcetype = mydlogs
index = mydindex

however, when the splunk process starts up, it shows errors like
ERROR TailingProcessor - matching /mydomain/logs/project/club/ against ^/mydomain/logs/project/myestlogs[^/]*.txt$

why it is looking at subdirectory, when recursive is set to false? how to avoid these ones?

Tags (1)
0 Karma

MuS
SplunkTrust
SplunkTrust

Hi lakshman237

The docs http://docs.splunk.com/Documentation/Splunk/5.0.1/admin/Inputsconf say about recursive:

recursive = [true|false]
* If false, Splunk will not monitor subdirectories found within a monitored directory.
* Defaults to true.

but as in your stanza you are monitoring a file and not a directory.

Since you use black- and whitelists; What happens, if you change your monitor stanza to match only the path but not a wildcarded file?

Verify your settings with splunk list monitor and checked the result?

cheers,

MuS

lakshman237
Path Finder

Thanks MuS. I can change the monitor stanza to look at the directory and change the whitelist to allow it. I'll test that out. The reason i had them separately, was there a lot of files on that directory, i wanted them get handful of them to a given sourcetype and others to another... ( possibily this could also be controlled via whitelist)

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...