topic Re: inputs.conf wildcards don't work in Getting Data In

inputs.conf wildcards don't work

tony_luu — Sat, 13 Jul 2013 00:06:04 GMT

=== Splunk 5.0.2 ===

I'd like to monitor these files, where "manydirs" is a wildcard:

/my/path/manydirs/error/*.log

so, my monitor stanza looks like this:

[monitor:///my/path/*/error/]
disabled = false
index = myindex
sourcetype = myerrors
recursive = false

also tried this:

[monitor:///my/path/*/error/*.txt]

splunk list monitor shows the correct path.
and no TailingProcessor errors
Yet nothing got indexed.
The doc sounds pretty straight forward but didn't work.
Very frustrated. Please help.

Thanks, Tony.

Re: inputs.conf wildcards don't work

okrabbe_splunk — Sat, 13 Jul 2013 02:03:28 GMT

You need to use ... to recurse multiple levels of directories.

[monitor:///my/path/.../error/*.log]
disabled = false
index = myindex
sourcetype = myerrors

Re: inputs.conf wildcards don't work

tony_luu — Mon, 15 Jul 2013 20:33:48 GMT

Gotta clarify my problem.
I don't want recursive, but rather many different directories at the same level where '' is,

i.e

/my/path/core/error/.log

/my/path/supp/error/.log

/my/path/misc/error/.log

...

I guess i could use the recursive '...' route, but even that didn't work for me.

Re: inputs.conf wildcards don't work

landen99 — Thu, 24 Nov 2016 19:26:21 GMT

why did you make it your accepted answer then?