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!

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...

Introducing Splunk Enterprise 9.2

WATCH HERE! Watch this Tech Talk to learn about the latest features and enhancements shipped in the new Splunk ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...