Splunk Enterprise Security

Unable to have Splunk index logs centrally stored on NAS

Ruts
Loves-to-Learn Lots

New to Splunk.

Attempting to have Splunk monitor and index logs from NAS. Logs are being centrally stored on a NAS from multiple clients. Need Splunk to look at the Network drive and index the logs in the shared folder.

Using UNC path (\\192.168.xxx.xxx\sharefolder\filepath).

Under the monitored files and directories in Splunk, able to monitor the number of log files in the selected directory and instantly show changes made if log files are added or removed.

Splunk account given administrator access to rule out privilege issues. Logged into Splunk service account and confirmed able to access network location.

If I take the same files and place them in a local folder, and attempt to index them using the same method, they are instantly indexed.

The problem appears to be with Splunk not ingesting and indexing the logs when pointed to the network location.

Any help would very much appreciated.

Labels (1)
Tags (3)
0 Karma
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...