Splunk Search

wildcards and inputs.conf -- directory recursion

Steve_G_
Splunk Employee
Splunk Employee

Trying to understand exactly how directory recursion works in inputs.conf.

Specifically, how does /foo/.../.../.log resolve? Does it recurse through the same set of directories as /foo/.../.log ?

Also, can you use "*" in a directory segment to narrow things down a bit? For example: /foo/b*r/.log instead of /foo/.../.log ?

Tags (1)
1 Solution

bwooden
Splunk Employee
Splunk Employee

Yes, monitoring...

/foo/.../.../.log

would monitor .log as would the preferred

/foo/.../.log

Additionally, you can use an asterisk within a path as you reference in

/foo/b*r/.log

...to monitor either /foo/bar/.log or /foo/banbar/.log but neither /foo/bar/lorem/.log nor /foo/lorem/bar/.log

The reason is that 3 consecutive dots represent recursing through any number of directories while an asterisk is a wildcard.

View solution in original post

bwooden
Splunk Employee
Splunk Employee

Yes, monitoring...

/foo/.../.../.log

would monitor .log as would the preferred

/foo/.../.log

Additionally, you can use an asterisk within a path as you reference in

/foo/b*r/.log

...to monitor either /foo/bar/.log or /foo/banbar/.log but neither /foo/bar/lorem/.log nor /foo/lorem/bar/.log

The reason is that 3 consecutive dots represent recursing through any number of directories while an asterisk is a wildcard.

Get Updates on the Splunk Community!

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...

Stay Connected: Your Guide to October Tech Talks, Office Hours, and Webinars!

What are Community Office Hours? Community Office Hours is an interactive 60-minute Zoom series where ...