topic Re: UNC Path with $ sign in Getting Data In

UNC Path with $ sign

peter_gianusso — Fri, 14 Sep 2012 14:05:51 GMT

We have an UNC name in the inputs.conf

monitor://\njros1bva0597\d$\LogFiles\W3SVC1\*.log

I suspect our share, d$, is the problem as to why this is not working. When it gets converted to regex, I think $ is a special character in regex.

Any suggestions? We can't change the Windows share name.

Re: UNC Path with $ sign

bwooden — Sat, 15 Sep 2012 14:41:02 GMT

Monitor statements proper support wildcard matching (*) and recursive directory matching (...). Regular expressions can be used as monitor options, for whiltelist and blacklist as an example, but the dollar sign shouldn't be causing problems here.

Is Splunk running as a local system account or as a domain account with network privileges? If it is running as a local system account it may not be able to access network shares. If that is the case the service will need to be configured to run as a service account with access to the network path.

Re: UNC Path with $ sign

peter_gianusso — Mon, 17 Sep 2012 16:08:55 GMT

Splunk does not like the d$ in the UNC path. It can't handle it. Must be an inputs.conf and props.conf approach.

inputs.conf
[monitor://\njros1bva0597d$LogFilesW3SVC1]
disabled = 0
host = NJROS1BVA0621ABC
index=imaging
whitelist = .log$

Props.conf
[source::...\CAPPM*.log] sourcetype = SOURCE1