Getting Data In

fschange with \...\

mcbradford
Contributor

This is my inputs.conf

[fschange://C:\Users...\AppData\Local\Microsoft\Windows\Burn]
index=windows
recurse=true
sourcetype=opticalmediaburn
pollPeriod=60
followLinks=true
fullEvent=true
delayInMills=1000

I see this in my _internal log

FSChangeMonitor - Monitoring file or directory that doesn't exist at startup time - //C:\Users...\AppData\Local\Microsoft\Windows\Burn

What am I doing wrong. The file/path does exist

Tags (1)
0 Karma

dmaislin_splunk
Splunk Employee
Splunk Employee

You should be using [fschange:] not [fschange://]

Something like this:
[fschange:C:\Users\AppData\Local\Microsoft\Windows\Burn]

0 Karma

mcbradford
Contributor

I changed the syntax to:

[fschange:C:\Users...\AppData\Local\Microsoft\Windows\Burn]

and it is still not working.

Can you use ...\? There are lots of users, so we would not be able to specify a different path for each user.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...