Getting Data In

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

agneticdk
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.

Regards
André

0 Karma

woodcock
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

agneticdk
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!

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 ...

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

Using the Splunk Threat Research Team’s Latest Security Content

REGISTER HERE Tech Talk | Security Edition Did you know the Splunk Threat Research Team regularly releases ...