Getting Data In

windows wildcard path name bug

nowakdaw
Path Finder

Hello All,

I searched on answers but I can't seem to come up with a clear answer. Has anyone figured out a workaround for the "Warning: In Windows, you cannot currently use a wildcard at the root level. For example, this does not work:[monitor://E:\...\foo\*.log]" from http://docs.splunk.com/Documentation/Splunk/latest/data/Specifyinputpathswithwildcards

I am attempting to forward log files using wildcards in my monitor names. I am using Splunk version 4.3.2. Thank you for your help.

0 Karma

nowakdaw
Path Finder

Thank you all for your help. I accomplished this by pointing to the specific folder explicitly and then using whitelists to get the necessary logs out.@lguinn, thank you. @jkat54 Thank you, I also try this and see if it works.

0 Karma

lguinn2
Legend

Well, I would guess that you could use

[monitor://E:\dir1\...\foo\*.log]

[monitor://E:\dir2\...\foo\*.log]

[monitor://E:\dir3\...\foo\*.log]

etc.

But there are probably other work-arounds as well. What directories do you want to monitor? Can you give us more details on what you are trying to do?

0 Karma
Get Updates on the Splunk Community!

Earn a $35 Gift Card for Answering our Splunk Admins & App Developer Survey

Survey for Splunk Admins and App Developers is open now! | Earn a $35 gift card!      Hello there,  Splunk ...

Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...

You’ve probably heard the latest about AppDynamics joining the Splunk Observability portfolio, deepening our ...

Monitoring Amazon Elastic Kubernetes Service (EKS)

As we’ve seen, integrating Kubernetes environments with Splunk Observability Cloud is a quick and easy way to ...