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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...