Getting Data In

Wildcard magic in monitor stanzas- Need help with inputs.conf

vgrote
Path Finder

Hi,

we have a directory with daily log files I want to read into Splunk 8.1.5:

/dir1/dir2/dir3/dir4/file-20220309.log, file-20220308.log, ...

Version A, working: "[monitor:///dir1/dir2/dir3/dir4]"

Version B, working: "[monitor:///dir1/*/d*/dir4/*]"

Version C, failing: "[monitor:///dir1/*/d*/dir4]"

Version C would in theory match the example of "[monitor:///apache/*/logs]" in the documentation, wouldn't it? That is, as long as "logs" is a directory.

Do I miss something here? Do I see a bug? Is there a limit on the number of wildcards in a path?

Puzzled in Hamburg

Volkmar

Labels (2)
0 Karma

SanjayReddy
SplunkTrust
SplunkTrust

Hi @vgrote 


for Version C,"[monitor:///dir1/*/d*/dir4]"

can you please share the exact location for  [monitor:///apache/*/logs] 

and have you tried using (...) intead of * 

0 Karma

vgrote
Path Finder

Hello SanjayReddy,

" [monitor:///apache/*/logs] " is mentioned as an example in https://docs.splunk.com/Documentation/Splunk/8.1.5/Data/Specifyinputpathswithwildcards#Input_example....

"/.../" would recurse into all subdirectories, which could be quite a long journey leading potentially across unknown directory structures, plus I got version B working anyhow which is probably taking less time.

I just wonder if it works as documented.

Kind Regards,

Volkmar

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In January, the Splunk Threat Research Team had one release of new security content via the Splunk ES Content ...

Expert Tips from Splunk Professional Services, Ensuring Compliance, and More New ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Observability Release Update: AI Assistant, AppD + Observability Cloud Integrations & ...

This month’s releases across the Splunk Observability portfolio deliver earlier detection and faster ...