Getting Data In

Why are some Windows event logs indexed in Splunk with a future timestamp?

Path Finder

Hi all

I have a search like this:

index=\* earliest=+1m latest=+30h sourcetype="WinEventLog:Sys*" Message=\*Upgrade\*

It looks at events in the future.

I have a customer that has some events in the future and it looks like it may be related to a restart of the system, maybe only after upgrading the OS.

And it may be related to the machine not having the correct time set when it starts logging, and only after getting the NTP server it logs correctly.

Any of you guys have had same issues? Any comments / feedback would be appreciated.

My guess is it is a Windows problem, not a Splunk problem.


0 Karma

Esteemed Legend

If you are using Splunk's built-in WinEventLog input, the only way for this to happen is for the system clock on the forwarder to be incorrect because this is the time that is used for all events and the Indexer does not have anything to do with modifying it.

0 Karma

Path Finder

Yes, so if the server after a restart, maybe only in context of an OS upgrade, has a wrong system clock set until it gets a hold of its NTP server, it could yield some events that are off.

I may have been unclear in my question above. The "looks like it may be related to a restart of the system". The "system" is the OS the forwarder runs on.

0 Karma
Get Updates on the Splunk Community!

Registration for Splunk University is Now Open!

Are you ready for an adventure in learning?   Brace yourselves because Splunk University is back, and it's ...

Splunkbase | Splunk Dashboard Examples App for SimpleXML End of Life

The Splunk Dashboard Examples App for SimpleXML will reach end of support on Dec 19, 2024, after which no new ...

Understanding Generative AI Techniques and Their Application in Cybersecurity

Watch On-Demand Artificial intelligence is the talk of the town nowadays, with industries of all kinds ...