Getting Data In

Inputs.conf "MonitorNoHandle" event start date issue

riegelo
Engager

We are pulling in DNS debug logs from windows servers and I have a few servers that have been running for awhile, but I have we are now adding inputs to pull in the event logs now. After pushing out the new inputs to the UFs, I noticed that the log files must have data starting around March of this year. At the rate it is ingesting we won't ever catch up and I don't need to be pulling in that old data.

We are using the "MonitorNoHandle" within the inputs to do so, but from my research I can't find any switches that will allow me to start collecting the "new" events only going forward. I found that the windows monitors has the "start_from" parameter, but that does not seem to work/apply to the MonitorNoHandle stanza from what I can tell. Are there options I am missing that would do this?

Labels (1)
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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...