Getting Data In

Multiple Wildcards in inputs.conf

mkelderm
Path Finder

Hi,

Can I use the following expression in my inputs.conf

/data/logs/kim/.../**MS?.log.gz*

Or

/data/logs/kim/.../*stderr*

Tags (1)

yannK
Splunk Employee
Splunk Employee

The simple wild cards for path are : * and ..., they are automatically replaced by regexes
see http://docs.splunk.com/Documentation/Splunk/4.3.3/Data/Specifyinputpathswithwildcards

It is not recommended to use regexes in the path (need to start to escape any special characters, by example file.txt has to be file\.txt ), instead you can use whitelist and blacklists that can contain regexes.

so with your case,
[monitor:///data/logs/kim/.../*MS?.log.gz]
has to be something like


[monitor:///data/logs/kim/...]
whitelist = .*MS?\.log\.gz

while the second should work because it uses only wildcards.


[monitor:///data/logs/kim/.../stderr]

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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...