Getting Data In

Input source path case sensitive?

eugenekogan
Explorer

Is the path specified in a monitor stanza in inputs.conf case sensitive?

For example, [monitor://C:\Windows\System32\dhcp] does not seem to work on servers that use the path of C:\WINDOWS\system32\dhcp. It's the same path except for capitalization of directory names.

If this is correct, is there a way to make it not case sensitive?

Thanks!

Tags (2)

jacobappleton
Explorer

While I haven't been able to find anything in the documentation, in my experience, yes, Windows paths are case-sensitive.

0 Karma

tgow
Splunk Employee
Splunk Employee

If you are having problems then I would suggest that you take advantage of wildcarding for directories which is available. Here is an example:

[monitor::C:\...dhcp]

or

[monitor::...System32\dhcp]

Here is a link to more information:

http://docs.splunk.com/Documentation/Splunk/4.3/Data/Specifyinputpathswithwildcards

gbronner_rbc
Explorer

The original poster asked a reasonable question, which is that while files are case-sensitive on Unix, the convention is that they are not on Windows. Hence, this behaviour, if confirmed, would be uncommon, and deserves to be highlighted.

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!

Tuning Edge Processor in Hybrid Mode: What Limits Each Data Path

When you run Edge Processor in hybrid mode, alongside a Splunk heavy forwarder on the same host, two questions ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Request for Professional Development: Attending .conf26

Winning Over the Boss: Your Pass to .conf26 conf26 is going to be here before you know it. If don't already ...