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!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...