Getting Data In

inputs.conf configuration help ..

rakesh_498115
Motivator

Hi.

I have source files in the following folder

path : splunkInput/logs/

Files in the path are
Managed1.txt
Managed2.txt
Managed3.txt
Managed4.txt
....
....
....

Managed50.txt

I have 50 Files like this..

Now i have given this configuration in inputs.conf to index only first ten files..ie.Managed1.txt to Managed10.txt.

So i have like this in inputs.conf

inputs.conf

[monitor:///splunkInput/logs/Managed[1-10]{2}.txt]
disable=false
sourcetype=mydata

but this is not working ..can u help the correct regex expression for this sceneraio.

Thanx

0 Karma
1 Solution

kristian_kolb
Ultra Champion

I think you'd better work with whitelists/blacklists in this case. I don't think that [monitor] stanza header can make use of full regexes.

[monitor:///splunkInput/logs]
sourcetype = blaha
index = blaha
whitelist = Managed1\d?\.log

Hope this helps,

Kristian

View solution in original post

kristian_kolb
Ultra Champion

I think you'd better work with whitelists/blacklists in this case. I don't think that [monitor] stanza header can make use of full regexes.

[monitor:///splunkInput/logs]
sourcetype = blaha
index = blaha
whitelist = Managed1\d?\.log

Hope this helps,

Kristian

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!

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...