Splunk Enterprise Security

Unable to have Splunk index logs centrally stored on NAS

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
Get Updates on the Splunk Community!

Data Preparation Made Easy: SPL2 for Edge Processor

By now, you may have heard the exciting news that Edge Processor, the easy-to-use Splunk data preparation tool ...

Introducing Edge Processor: Next Gen Data Transformation

We get it - not only can it take a lot of time, money and resources to get data into Splunk, but it also takes ...

Tips & Tricks When Using Ingest Actions

Tune in to learn about:Large scale architecture when using Ingest ActionsRegEx performance considerations ...