Getting Data In

can splunk monitor fschange

nagarjuna280
Communicator

I want to know the user details, what changes happened, when, if someone makes changes to config files. is that possible?
I tried something below, I got events as

6/14/10 9:20:52.000 AM Mon Jun 14 09:20:52 2010 action=add, path="C:\TEMP\configs.txt", isdir=0, size=388, gid=-1, uid=-1, modtime="Mon Jun 14 09:17:56 2010", mode="rwxrwxrwx", hash=

[monitor://\192.168.1.12\Siteroot\Web.config]
disabled = false
index = _audit
sourcetype =dfgd
pollPeriod = 60

and when I tried to set up this config in Splunk forwarder, I didn't get any results.

Tags (2)
0 Karma

inventsekar
SplunkTrust
SplunkTrust

from inputs.conf documentation -
http://docs.splunk.com/Documentation/Splunk/7.2.1/Admin/Inputsconf

[fschange:D:\Siteroot\web.config\]
fullEvent=true
pollPeriod=60
recurse=true
sendEventMaxSize=100000
index=main
sourcetype =dfgd

i think instead of monitor you should use fschange
and for index, we should not use _audit
(maybe -index=mainORsomething)

EDIT - thanks @harsmarvania57
Please keep in mind that this feature is deprecated and will be removed in future version of Splunk. Please see documentation http://docs.splunk.com/Documentation/Splunk/7.2.1/Data/Monitorchangestoyourfilesystem

 This feature has been deprecated as of Splunk Enterprise version 5.0. This means that although it continues to function in version 6.x of Splunk software, it might be removed in a future version. As an alternative, you can:

     Learn how to monitor file system changes on Windows systems.
     Use the auditd daemon on *nix systems and monitor output from the daemon.

 For a list of all deprecated features, see the topic Deprecated features in the Release Notes. 

harsmarvania57
Ultra Champion

Please keep in mind that this feature is deprecated and will be removed in future version of Splunk. Please see documentation http://docs.splunk.com/Documentation/Splunk/7.2.1/Data/Monitorchangestoyourfilesystem

This feature has been deprecated as of Splunk Enterprise version 5.0. This means that although it continues to function in version 6.x of Splunk software, it might be removed in a future version. As an alternative, you can:

    Learn how to monitor file system changes on Windows systems.
    Use the auditd daemon on *nix systems and monitor output from the daemon.

For a list of all deprecated features, see the topic Deprecated features in the Release Notes. 
Get Updates on the Splunk Community!

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...