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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Register to Attend   Join our Tech Talk ...

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...