Getting Data In

Splunk - Adjusting source file timestamp

nageshkumarapp
New Member

Given:
I have two log files (file_1, file_2)
Each from a different server (server_1, server_2).
The servers are not property synchronized via ntpd. (Example: server_1 is 13 seconds ahead of server_2.)
I do not have the ability to adjust or correct the server times.
I am the Splunk user, not the Splunk administrator.

Problem: After ingesting each of the log files, the events are off by 13 seconds (obviously).

Question: Can I adjust the _time for all events in source=file_2 by 13 seconds so the events line up correctly in search results, graphs, etc.?

0 Karma

jkat54
SplunkTrust
SplunkTrust

You can do it in search like this:

  ...| eval _time=if(host=server_2,_time+13,_time) | convert ctime(_time)

_time equals (if server_2, add 13s to_time, else use _time)

The eval will end up changing _time to epoch in visualizations... add the convert to swap it back to human readable format.

You can do it in search time props like this (maybe, just not sure if it works with _time)

 [host::server_2]
 EVAL-_time = _time+13

Cheers,
JKAT

cpetterborg
SplunkTrust
SplunkTrust

You will have to regularly check the time drift and update accordingly (or automate it) because unchecked system time will continue to drift further

You COULD also use the index_time instead of _time for your searching, though that could have a little bit of latency (but hopefully not 13 seconds worth). That won't require the updating of the time drift.

jkat54
SplunkTrust
SplunkTrust

I concur!!!

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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...